3 replies to this topic

[parkerdg]

Hello,

I am trying to find a way to keep my users from having to log into multiple related files.  I have over 100 users in one file and have now related this file to another existing file.  There does not seem to be a way to migrate account information from one file to another, so I thought about using guest access.  I would say about 75% of the users do not need access to the related file, but are constantly prompted when going to do a sort or export, for example, to log into the related files, for which they must enter "cancel".  The other 25% of the users do need access to the related data and have accounts in that related file.

Unless users do something such as a Sort, everything is fine.  Most don't need access to anything in the related file.  Is there a way to get around this access issue?  Something that would log users into the related file using the account on the file and if they did not have an account to use the guest account?

I dislike the idea of setting up temporary passwords in the related file for everyone to then have to change.  My users will be quite confused if I were to do that.  While I expressed this issue as one related file, the reality is that there a multiple files related to the base file and the user gets multiple log in messages which appear identical to the user and they think they are getting the same message over and over.  Part of this is a design flaw, but that is what you get when you carry over files built in version 6!  I have made it from 175 databases down to 50 by combining files, but I still have many more to go and clearly did not handle the security fully to handle this situation.

Many Thanks.
Deborah

[Steven H. Blackwell]

You might look into setting up External Server Authentication.  That way you have to create the Accounts in only one place.

Steven

[Mr. Scott]

But what about a local UI file in a data separation model? And, how do I ensure the UI File operates with the same privileges as the Data File that uses EA?

I posted details at:
Security a data separation model

[Steven H. Blackwell]

The Separation Model™ refers to the separation of the data from the Ui and business logic.  it does not mean that the Ui file goes on the local workstation.  The Ui file(s) belongs on the server as well.

Steven