I have multiple databases that are related together by saledates. If a person was to enter the program, they would enter the saledate they wanted to work in at the entrance of the program and everything in the program would be related to that saledate. For example:

Enter: [saledate] (8/5/2003) Press

In stead of using a relation with only the date you could use a concatenation of username and date field.

Ernst.

That would be a great idea, but don't I have to setup a password file so that they could enter a username?

If your users are on different machines (or login with different usernames on the same machine) then the answer is no, just use Status(CurrentUserName)

Otherwise you could use a password file, or just a custom dialog in the startup script.

Ernst.

If I wanted to setup a password file and wanted to check to see if the person signing in is the correct user with the correct password, would I setup the script as:

If password::g_username = "Sally" and password::g_userpassword = "DOG"

go to layout "DataEntry"

EndIf

with the g_username and g_password being in the fields in a new file called password? Also how would I verify that this person is in the password file, in other words out of a list of 20 users, how does it know to check the file to see if the user is there?

I don't claim the following is the safest and/or easiest way to make a login system (there are several examples in the 'samples' section of the forum) but you could make a relation from your global username entry field to the username field in your password file.

The construction in the login script could then check if the global password entry field matches the password field in the password file:

If password::userpassword = g_userpassword

go to layout "DataEntry"

EndIf

Regards,

Ernst.

If you made your saledate field a global, it would be different for each user. That might be the simplest way to go.

Hey Fitch, I re-read the original question, and you are right.

Respect,

Ernst.

So Fitch are saying that if two different users Jane and Sally both entered the system under their unique login and both entered using a global field as a date field and Sally entered the sale 5/4/2003 and Jane entered the sale 7/8/2003 that the computer would know that sally was working with sale 5/4/2003 and Jane was working with sale 7/8/2003?

Hi Dobbers ...

Yes.

When users access a multi-user database (through "Hosts" in the Open dialog), data entered into global fields by each user is unique for that user. So, in your system, if you have a global date field (gDate), and Sally enters "5/4/2003" and Jane enters "7/8/2003," Sally and Jane will each be working with different data sets based on their individual entries into the gDate field.

The value entered into gDate can then be referenced for Finds, for default date entry into new records, or whatever other date-specific operations for which you may want to use the global value.

When the user exits the multi-user database, the gDate field returns to empty.

Thank you for clearing that up Jim.