--------------------------------------------------------------------------------

I have a dilema on my hands as I can't seem to figure out the best way to accomplish this. I created a database to handle all of our letters for my department in the company. The problem I am having is that we have 26 people who could possible access the database at the same time. The letters are created using a form. (not a problem with multi-users) When someone wants to print the letter the do a search either by "Letter Date", "Provider Name", "Provider Number", or "Group Name". I set it up so either one of these search queries append data into one table called "Letter Report Information" all 38 letters get there data from this 1 table. The problem I am having is that if John and Mary try to pull different/same letters at the same time or while one is viewing their letters the data is getting pushed onto the others Letter.

Example:

Mary goes to print her Welcome letter
John also goes to print his Denial letter at the same time

When John's letters show up.. the Denial letter shows up with his data, but also with Mary's Welcome letter data.

What can I do or what kind of query can i use to avoid this problem as it is becoming a very prominent issue? ::Please Help::

Thanks.

If they login, you can use their username as a row identifier.
As another option, some other unique identifier, not 100%, but pretty close is using timer as a unique identifier.

You just gave me another idea.. Is there anyway that I could capture the persons Computer UserID when the initially create the letter and then have that field on the report hidden with some kind of code that would say...

If [User ID] <> ("Field [User ID] on Report") Then
Somehow only show the letters for the person who created them and not show any letters with a userid different from their own?