Transfer accounts to another file

[stuj1026]

Please Help !!

We have converted a 50 file solution from FM6 to FM7.. Everything is working fine. Due to the size and time restrictions of this solution we did not have the time to create a single database with multiple tables.

We have sold our solution and provide support to them and we regularly provide updates. I was able to create scripts that when the administrator creates a new account for a user it creates the login and password in the other 49 files along with privelege sets that have been setup previously. The login is maintained in the admin.fp7 but the password is just entered into a global field and passed as a script parameter to be used as a setup in the other 49 files.The password is not maintained only created for each file in the solution.

Our problem now comes in when we have to upgrade one of the 49 files.. Lets call that billing.fp7. We might make some changes to the structure or add some fields at our location. We can then get their file and import the data but what do we do about the logins and passwords. I can script the update of the logins as this is maintained in admin.fp7 but the passwords ??

I think we are stuck on this issue.. And we do not see anyway around this Can anyone offer any suggestions??

Thanks Stu

[Steven H. Blackwell]

The accounts can be transferred, but the passwords can not be, isnce they aren't stored in the file.

Steven

[R2D2]

Hi !

I have this same problem In my solution I have several databases due to different things they serve for. Do I have to create access privileges to EVERY single file for EVERY user ?? And if I add a user do I really have to add it to every database ? Is there a simplier solution ? I do not use a server.

Arttu

[Fenton]

stuj1026, about the only thing I can think of is to have a script to create the accounts in the one (or several) specified new file, with the option "User must change password on next login," using a known generic password.

Maybe your Account creation scripts are like that already. That would be good.

The "specified" file(s) can be managed with either a checkbox or radio button list of all the files in the solution. Then a long "If, ElseIf" script to run the script in the choosen file(s); since we can't dynamically specify which file/script to run.

Each user would then enter their password next time they logged in (hopefully correctly), as the new password, and it would be set.

Arttu, you normally create an Account for each person (though you don't really have to), but only one Privilege Set for each "type" of user. Usually several Accounts have the same Privilege Set. A Privilege Set is about "what kind of access and what actions can be done in this file."