exclusive access error

[gilescis]

I have a small dabase shared by 4 users on the network. when someone opens the db, then someone else opens it there is no problem. when user 1 has a report open and user 2 tries to update a record, user 2 gets the following error

You do not have exlcusive access to the database at this time. If you proceed to make changes you may not be able to save them later

I have split the database into 2 seperate Db's one is the tables only the other is the objects.

Please advise this is getting frustrating

Thanks

 

[KeithG]

It is becuase user one has the records locked. I see that you tried to change the database to a FE/BE. You should only put the back end on the intranet or network and the front end on each of the users machines and link the tables.

 

[gilescis]

ok but one small problem, I have a few users that have thin clients that connect via RDP to our Terminal server, then I have 3 users that have pc's

If I copied the FE to the 3 users pc, when ever I do an update I have to update each pc ?

What about my thin client users

 

[KeithG]

I am not sure what a thin client is?

 

[gilescis]

Basicly its a dumb terminal. It connects to a Windows 200 Terminal server and runs all the apps from the server. Word, Excel, Access, Accounting software etc....

 

[gilescis]

Still need some help on this issue Anyone have any Ideas

 

[Len Boorman]

Basically what is happening is exactly what should happen. If somebody is currently generating a report you cannot have those records being changed at the same time.

I am a little confused by the message about not being able to save changes along with exclusive access.
Is every body using the same Access version ?.

The record lock on a Report being open I can understand but it seems curious that you are getting this with only 4 users. maybe you are being very unlucky. How long is the report open for.

Think there is more in this.

You need to be very specific regarding Access version and exactly who is doing what at the instance you get the error message. Can you generate the problem on purpose. If so this would allow you to state precisely the circumstances. How is report being generated.

On the update what record locking strategy do you have in place. Does the report contain the record you are trying to update

Len

 

[gilescis]

I think I got it figured out, I had to copy the FE to each users home dir so they con run seperate instanceses of the FE db, But my question now is when I make a change to a form or report etc , do I need to copy that file over to each users home dir and overwrite the copy thats already there?
or is there an easier way of pushing out the updates

Thanks

 

[Len Boorman]

But my question now is when I make a change to a form or report etc , do I need to copy that file over to each users home dir and overwrite the copy thats already there?
or is there an easier way of pushing out the updates

Thanks

You can export it to each instance so basicallyI think the answer is yes

L

 

[gilescis]

ok Thanks for the help