Dropped connection causing corruption—should I change configuration? 1

[BoulderRidge]

I have an Access 2007 app running in a Windows 7/Access 2010 environment. The back end database lives on a network server. The users connect wirelessly to the network on tablets (no other option).

Currently each user has a personal copy of the front end application database (with tables linked from the back end database) in a separate folder on the same network server. They launch the application from a shortcut on their tablet that opens their unique copy of the application database living on the network server.

We have chronic problems with the wireless connection dropping when users are in certain parts of the building and this is beyond our control. We also have chronic problems with the back end database getting corrupted and this corruption seems to correlate to instances of a tablet wireless connection dropping while the user was in the front end application.

Would it be better to install a personal copy of the front end application database on each user’s tablet rather than having them run it from the network? Either way is dependent on the wireless connection to the server, but maybe this would help a disconnected front end application exit more gracefully? It will take some effort to make the change so I’m interested in anyone’s expertise or experience with either scenario.

thanks,

-- BoulderRidge B-)

 

[PHV]

Would it be better to install a personal copy of the front end application database on each user’s tablet
My answer is: YES

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[lameid]

Step 2 would be to use unbound forms and write error handling to deal with the backend not being available... Good luck.

Set your backup strategy to paranoid and remember that in use database backups aren't necessarily functional...