How to avoid Access corrupt?

[Lisa]

Hi,

Our Access database is corrupted whenever user disconnect from it
unexpected. For example, if the user work remotely, they use VPN to connect
to the office, then log into the program. but if the Internet is disconnected
unexpectedly, user exit the program not correctly, then the Access would be
corrupted. How to avoid this happen. Please help!

Thanks in advance!

Lisa

 

[Larry Linson]

Three excellent sources on avoiding corruption in Access databases are MVP
Tony Toew's website at http://www.granite.ab.ca/accsmstr.htm, MVP Allen
Browne's website at http://allenbrowne.com/tips.html, and former-MVP Jeff
Conrad's "Access Junkie" site at
http://www.accessmvp.com/JConrad/accessjunkie.html.

Even if you are using Terminal Services via a VPN, you need to split your
database so that each user has their own frontend database (queries, forms,
reports, macros, and modules) linked to tables in a backend database
(tables, data, and relationships) in a shared.

You can also use a (true) server database, with each user having their own
copy of an Access client application.

But you'll find much more information, in detail, at the referenced sites
above.

Larry Linson
Microsoft Office Access MVP

Hi,

Our Access database is corrupted whenever user disconnect from it
unexpected. For example, if the user work remotely, they use VPN to
connect
to the office, then log into the program. but if the Internet is
disconnected
unexpectedly, user exit the program not correctly, then the Access would
be
corrupted. How to avoid this happen. Please help!

Thanks in advance!

Lisa

__________ Information from ESET Smart Security, version of virus signature database 3990 (20090406) __________

The message was checked by ESET Smart Security.

http://www.eset.com

 

[Sylvain Lafontaine]

As you have noticed by now, you cannot use Access on any network that's not
rock solid and the use of a VPN is no exception to that. You have two easy
solutions to that that will probably each works in your case:

1- Use Remoting (aka Terminal Serveur, Thinsoft, Citrix, etc.): the Access
program is run remotely directly on the server, so there is no WAN network
(the VPN in your case) between the Access application and the backend
tables.

2- Replace the JET backend with SQL-Server.

Other possibilities would be to rewrote the program using some other
technology such as ASP.NET.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain2009 sylvainlafontaine com (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)