Splitting Database Issue

[CyndyG]

Before I split the dtabase it was being mapped to across several states
within our organization. I decided to split the database because access was
slow and corruption was taking place a lot.
ok,so I split the dtabase put my backend on the server and used unc for the
link path.
Problem. I have 2 users at a site where one can open the database click a
button that opens a form for addining or editing records. The other one can
open the database but,when the user clicks the button nothing happens. So I
stated watching the backend when the user clicked one of the buttons,the ldb
went away. First I thought it was because the user neded to be on the same
server as the backend,which turned out to be false because the other user
wasn't on the same server as the backend was and had no problems. Everyone
using the database have the rights to it and had no problem when they were
mapping. THe front end was sent to 9 users,3 can not use the front end.
Help,please.

 

[Dale Fye]

Cyndy,

In my experience, Access is not a great tool for the backend when being used
over a wide area network. I recommend you read the following article.

http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html

Dale

 

[Arvin Meyer [MVP]]

Unless you are using Terminal Services, or a web-based front end, Access is
not suitable for use on a WAN. Dropped connections will often corrupt the
database. I recommend changing the back-end to a SQL-Server Express
back-end. Being a server based processing engine, corruption will not be
much of a problem.

That said, this isn't your problem. I believe that some users are trying to
open exclusively and cannot because someone else is in the database. Also
check the mappings and make sure they all point correctly. And last make
sure that server permissions include create and delete. If they don't, they
will not be able to create or delete an ldb file and may be blocking
themselves.

 

[GBA]

yep, your issue really is not "splitting database"; your issue is running a
desktop application remotely across a WAN.

it is actually not an Access issue per se, it would be universal to any
desktop application.

which is why you want Terminal Services; because this is the industry
solution for this situation. also to keep in mind that with Terminal
Services you still want the split database and an FE assigned to each user's
TS session. It may be possible with the newer TS Gateway server to have a
pool of FEs...not sure...

 

[Armen Stein]

That said, this isn't your problem. I believe that some users are trying to
open exclusively and cannot because someone else is in the database. Also
check the mappings and make sure they all point correctly. And last make
sure that server permissions include create and delete. If they don't, they
will not be able to create or delete an ldb file and may be blocking
themselves.

Or, is it possible that the back-end server isn't Windows?

We once saw an LDB disappear from the back-end folder when the
*second* user opened the application. We also had catastrophic
corruption issues. Turned out that without anyone realizing, the
back-end mdb was on a Unix server. Access isn't supported for
Unix/Linux.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

 

[Arvin Meyer [MVP]]

Or, is it possible that the back-end server isn't Windows?

Perish that blasphemous thought! <lol>

 

[James A. Fortune]

Or, is it possible that the back-end server isn't Windows?

We once saw an LDB disappear from the back-end folder when the
*second* user opened the application. We also had catastrophic
corruption issues. Turned out that without anyone realizing, the
back-end mdb was on a Unix server. Access isn't supported for
Unix/Linux.

Armen Stein
Microsoft Access MVP
www.JStreetTech.com

I agree with Arvin. You wouldn't want to do that. The sudden increase
in speed and stability might frighten the users .

James A. Fortune
(e-mail address removed)