Author Topic: New User Password Issue  (Read 3803 times)


  • Member
  • *
  • Posts: 12
New User Password Issue
« on: February 09, 2011, 08:43:02 AM »
In a new installation of Core2 CRM w/ Invoices, we
  • login with the default admin user
  • change the admin password
  • create two new user accounts

However, the new users, and the admin password are not altered in the Invoice database. 

The FM files were renamed replacing "Core2" with "XYZ".  All file references (filename remains Core2 ABC.fm7, the file ref is simply changed to the file:XYZ ABC.fm7) in each file were corrected before any users were created. 

Is there a script step that would not update with this new information that wouldn't allow the new users to be created? 

Melinda DePalma

  • Member
  • *
  • Posts: 179
    • Productive Computing
Re: New User Password Issue
« Reply #1 on: February 16, 2011, 04:30:32 PM »
First I would like to confirm that you renamed the Core2 files using the FileMaker > Tools > Developer Utilities rather than just manually changing the file names. The Core2 CRM with Invoices consists of 5 separate FileMaker files. Did you use the Developer Utilities tool to rename all the 5 Core2 files as shown in the attached screen shot? If you did not, then the 5 files that make up the Core2 CRM with Invoices properly did not get properly linked and could be the root of your woes.

Please confirm before we continue troubleshooting.


  • Member
  • *
  • Posts: 12
Re: New User Password Issue
« Reply #2 on: February 17, 2011, 08:24:09 AM »
I did not.  I manually made the adjustments to the physical file name and then within each of the databases Manage->External Data Sources section.

What is my best option now?

Marc Larochelle

  • God
  • Member
  • *****
  • Posts: 3
    • Productive Computing, Inc.
Re: New User Password Issue
« Reply #3 on: February 18, 2011, 12:18:07 PM »

We are able to duplicate this scenario on our end.

Please see that attached screen shot.

Here's what happened:

• When we first deliver the Core2 with Invoices, we set the checkbox “Core2 with Invoices is Installed” ahead of time (as shown in the attached picture). FYI, this checkbox is a global type field so permanent setting of this field can only be done when the files are not being hosted.

• During the opening process of Core2, there is an area in the open sequence (preferences file/opening script) that double checks to see that the Core2 Invoices file is still available. If the file is not available for any reason, the script will deselect this box (permanently).   This is what happened to you.

• When you initially renamed your files and opened up the Core for the very first time, the internal file references had not yet been updated by you.  Because of this, the opening script ran and didn't find the appropriately named core2 invoices file and deselected the checkbox. From that point on, the checkbox was permanently disabled.  For several reasons (to lengthy to discuss in this post) this checkbox must be set manually if the invoice files is part of the system.   It will remained check permantely so long as the invoice file is available (and you don't manually rename it again).

• The checkbox must be checked in order for several functions in the Core2 to operate properly (specifically account editing and creation).

• If you had renamed the files using the FileMaker developer tool (FileMaker advanced) as Melinda pointed out, all files and internal references to those files would have been renamed properly and at the same time.  Therefore opening the Core2 for the first time after renaming with the developer tool would have properly identified the Core2 Invoices file and would have not deselected the checkbox.

So here's how you can resolve your situation from this point:
1) Remove your files off the server and open them as a single user using the admin credentials.
2) Manually select the checkbox in the preferences (as noted in the attached picture)
3) Re Edit the Admin account password (this should repair the password in the invoices file).
4) Re host the database and test adding a new account or editing an existing account password.

Note:  You may want to remove the existing accounts that were not created properly and re-add them (if you haven't already). You should be able to manually remove the partially created accounts using the traditional preferences area to delete accounts In the Core2.  In other words, you shouldn't have to go under the hood and manually delete accounts within each file, just use the preferences like you normally do.