Force Master Hunter
Sep 20th, 2001, 03:03:31 AM
I just want to understand what we want, because I saw a similar thing - right in one of the support databases we run right here - One account, many optional id's. Now, the functionality is based on the key field of the accout section of the database
Say this key field being email address. Effectively, the email address becomes the login, with registered accounts listed against it.
The database refers to the email address, picking out what accounts are associated with it.
* Thinking*
Then you need the right form, that would display the names associated at post time.
Yeah that coudl work, depending on hos thw accunts database is set up
Say this key field being email address. Effectively, the email address becomes the login, with registered accounts listed against it.
The database refers to the email address, picking out what accounts are associated with it.
* Thinking*
Then you need the right form, that would display the names associated at post time.
Yeah that coudl work, depending on hos thw accunts database is set up