Keep getting kicked out of access from 1 pc but works great on another

[emaluzer]

I am trying to solve a clients issue regarding MS Access 2003(?). The front computer at the shop can access the database and make all the changes, but if the back pc tries to open the file and make changes they get kicked off of the file. They said it use to take about 3 minutes for them to get kicked off and they could make changes in that time but then would get kicked off and the changes wouldnt be saved. Now they say it happens in only a few seconds. I dont really use Access so am not sure if there is a simple solution to this or not. Any suggestions would be greatly appreciated.



Sorry if there isnt enough info. Im just going by what they told me and havent seen it in action yet.

Edit: It only happens if the front computer has MS access up and running. If they turn it off then they can run it from the back computer and have no problems

[NTC]

define "kicked off" - that implies that you are in it ok - and then get some message or something that you are no longer connected....would like to know more about that...

both PCs should have their own FE linked to the common BE....is this the set up?

[emaluzer]

I guess kicked off isnt the right term. They explained it better to me and it seems that if the front pc has ms access up and running, then the back pc opens a same database file but it displays # signs and ? symbols. The cannot make any changes to it. From what I read it seems that is because the file is in Read only mode. so not so much as kicked off as they described it, but more like inaccessible to any file and a error message pops up. (they couldnt say what the error message said)

I dont think they both have their own FE. Could you explain this in a step by step fashion so I could try to do this for them? I know the front computer is where the database files are all kept. So would that be the BE? if so then the back computer needs to have its own FE?

[emaluzer]

This is the error message that comes when they access the file :

Disk or network error. (Error 3043)

An internal disk or drive failure prevents reading from or writing to the disk.
Possible causes:

• You tried to use a network drive, and the network is temporarily busy, or you are no longer connected to the network. Check the network connection, and then try the operation again.
• The disk or drive has failed.

[emaluzer]

any help at all please

[RuralGuy]

I dont think they both have their own FE. Could you explain this in a step by step fashion so I could try to do this for them? I know the front computer is where the database files are all kept. So would that be the BE? if so then the back computer needs to have its own FE?

Every computer that accesses the BackEnd need its own copy of the FrontEnd on that machine. Use the Linked Table manager to link to the BackEnd.

[emaluzer]

that I have to install access specifically on the 2nd pc and make a copy of the file then link it using the linked table manager?

Sorry if i dont get it, I dont use access just trying to solve a problem for a client. Laymens terms would be very appreciated.


Thank you very much for the help so far

[RuralGuy]

Access *always* executes on the local computer unless you are using something like Citrix.

[emaluzer]

what do you mean by front end then? please explain

[RuralGuy]

The BackEnd has *just* the tables and the FrontEnd has everything else.

[emaluzer]

so how do i setup a computer so it would work

[RuralGuy]

Here's some good links on the subject:
http://www.access.qbuilt.com/html/ge...1.html#SplitDB
http://www.accessmvp.com/TWickerath/.../multiuser.htm
http://www.accessmvp.com/JConrad/acc...splitting.html