G
Guest
Hi All
I have supplied a Runtime version of an application to a client which is
split into a FE/BE configuration. I am using Access 2003 and deploying onto
Windows XP
Each machine has a copy of the Front End and the backend was placed in its
own folder and setup so that it was visible and accessable on the nextwork.
At load time (i.e. when the user invokes the application) , the system
re-connects to the backend, updating all the table links in the front end. So
in this case, it is going across the LAN to the backend DB.
The problem I have is if Person A logs on, then Person B cannot - the system
waits until the first person has exited the system (and Vice-versa). I have
tried accessing the BE via the UNC and as a drive letter on both machines,
but still the same problem.
I haven't had this problem before, and can't think why it should occur -
Access is after all a multi user system, so has anyone out there got any
ideas as to what I should be checking? The only "lock" that I would expect
would be on the LDB, but the folder has been set up with write permissions,
and both machines can (independantly) access the drive and use the DB - so it
is not a persmissions problem.
Many Thanks
Chris
I have supplied a Runtime version of an application to a client which is
split into a FE/BE configuration. I am using Access 2003 and deploying onto
Windows XP
Each machine has a copy of the Front End and the backend was placed in its
own folder and setup so that it was visible and accessable on the nextwork.
At load time (i.e. when the user invokes the application) , the system
re-connects to the backend, updating all the table links in the front end. So
in this case, it is going across the LAN to the backend DB.
The problem I have is if Person A logs on, then Person B cannot - the system
waits until the first person has exited the system (and Vice-versa). I have
tried accessing the BE via the UNC and as a drive letter on both machines,
but still the same problem.
I haven't had this problem before, and can't think why it should occur -
Access is after all a multi user system, so has anyone out there got any
ideas as to what I should be checking? The only "lock" that I would expect
would be on the LDB, but the folder has been set up with write permissions,
and both machines can (independantly) access the drive and use the DB - so it
is not a persmissions problem.
Many Thanks
Chris