Restrict A Table To Only One Record?

[Mark Reed]

Not quite sure where to post this...

I am creating a tool for serveral people to use. It will be installed on each person's PC, and will be s stand alone - no network or unified database.

So each person will basically have thier own copy of this.

I have a table that will contain profile information that will be used everywhere else in the database.

Things like the person's name, phone number, email address, photo, ect...

Those elements will be used in conjunction with the data tracked - sales leads basically.

They will use the database to print forms that have these profile fields merged...

For example, one of the forms will be a followup letter that pulls thier name and address to include as the listed salesperson contact.

I could accomplish this by setting all the fields in the profile table to global, and use some type of security to restrict new records... but I wanted to check with those of you out there doing this already and see what is the best approach?

Would it be better to not make them global and still use security to limit the record?

Anyone have an example file they can share on creating a "profile or parameters table"?

[dansmith65]

I haven't done this type of thing before, but it looks like you are on the right track. Either method you mentioned should work fine (prevent creating and deleting records via security).

Would it make sense to host this file, allow each user to log into the hosted file and have it display only their record? This would make it much easier to provide updates.

It also sounds to me like the Forms could be new records in separate tables. Perhaps this is the case already, I don't know.