Kidnapped records

[MikeAngelastro]

Hi,

I have a situation where I have one mde on a server and four clients. So they all are using the same front end. I have implemented security so folks have to log in. The database has patients ( a patient table) with a treatment plan called a case (treatment plan table with a case number as the key). Each case can have more than one follow-up ( a follow-up table with a case number as a foreign key ).

My problem is that on occasion a client records a follow-up for a case but later finds that the follow-up is missing for the case. However, one of the other clients pulls up a different case and finds extra follow-ups for it. It's like the second case kidnapped the follow-ups for the first case.

Typically, the client is looking at a case on a form and clicks a "Follow-ups" button to view and/or add follow-ups. I had noticed that sometimes the case would not record in the follow-up form; so I added a global variable to store the case number and have the code invoke the follow-up form using the global variable instead of the textbox value that holds the case number. This solved the first problem but now I'm finding that on occasion Access stores a follow-up to the wrong case. I believe that this happens when there is more than one client is logged in at the same time.

I'm thinking that maybe I should create a front-end file for each client but I'm not sure if that will fix the problem of the wayward follow-ups.

I'm wondering if any of you has had this kind of problem and have found a solution. Perhaps there is a better way to set up this "client-server" application.

Thanks,

Mike

 

[Shep]

I can't say that I have experienced exactly your situation, but if several people have the same frontend copy open, it is inevitable that, sooner or later, variable values will be changed (or become empty) when you did not intend them to. To ill effect, I might add.

Place a separate copy of the frontend on each workstation.

You didn't mention whether you have separate front and back ends, now that I think about it. Do you?

If not, you need to split the thing. Then create an .mde from the frontend portion and distribute it to your clients' machines.

Shep

 

[MikeAngelastro]

Thanks Shep. I am using both a frontend and a backend.

Regarding one frontend for each user I will give it a try. I had considered that before but your suggestion reinforces the recommendation.

What I had been thinking, howver, was that, even if you use one frontend file for more than one user, all of the global vatiables are local to each client computer. Maybe that over simplifies it.

I think I'll do a front end for each user.

Thanks for your help.

 

[Shep]

Hmm...that is possible. You've pointed out something I did not make clear; that I was making an assumption. I am not 100% certain.

If globals are local to the client machine/environment, then you have another deeper problem. Something is causing the current record to change.

If a frontend allows the editing/adding/deleting of records, it seems wise to me to give each user their own copy - for several reasons, some of which I am surely not entirely clear on. Better safe than sorry, I guess?