Database Corruption

[helplessinhawaii]

I have a database in the US on a server. When this database is accessed from
a server in Gemany it will sometimes get corrupted. It appears that in times
of high traffic, the Access program will time out and the user will show
Program Not Responding in their task manager. When this happens, the next
user from the US will get the standard Database Corruption message. Is there
a way to extend the time for the program to open? Is there a way to fix the
corruption other than the Compact and Repair provided (This does not work).
Why would this corrupt the database? I know these are many questions & I
apologize.
Thanks for your help.

 

[Tom Wickerath]

JET databases are very suseptible to corruption from interrupted write
operations. There is a much higher probability of encountering corruption
when using a WAN (wide area network) versus the intended use which is a LAN
(local area network). Here are two articles on database corruption that are
good references:

Preventing Corruption (Allen Browne)
http://allenbrowne.com/ser-25.html

Corrupt Microsoft Access MDBs FAQ
http://www.granite.ab.ca/access/corruptmdbs.htm

Here is an article on the use of WAN's with Access, written by Albert Kallal:

Using a wan with ms-access? How fast, how far?
http://www.members.shaw.ca/AlbertKallal/Wan/Wans.html

I believe the only suitable solution, if you want to stay with the JET file
format, is to implement Terminal Server (TS). Albert's article discusses TS.
I suppose replication would also work, but I think support for replication
has been dropped in the new Access 2007, currently in beta. Oh, Sharepoint is
also a possible solution too, but one caveat is that one apparently has to
live without referential integrity (at least at the engine level) with a
solution that uses this technology.


Tom Wickerath
Microsoft Access MVP

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

 

[Douglas J. Steele]

Access isn't intended to be used over the WAN. Albert Kallal has a good
discussion of this at http://www.members.shaw.ca/AlbertKallal//Wan/Wans.html

 

[aaron.kempf]

ROFL

man you kids are hilarious

I used Access Data Projects across a WAN.. all day long; every day.
it works like a charm.

you kids really need to get a clue

 

[David W. Fenton]

I believe the only suitable solution, if you want to stay with the
JET file format, is to implement Terminal Server (TS). Albert's
article discusses TS.

Terminal Server is a very good solution for supporting users at
multiple sites supported by a WAN.

I suppose replication would also work, but I think support for
replication has been dropped in the new Access 2007, currently in
beta.

It hasn't been dropped. It is still available with A2K3-format (and
earlier) MDBs. It is not implemented in the new accdb format. This
means that it's in the same situation as DAO was starting with A2K
-- still quite usable though not being further developed.

Oh, Sharepoint is
also a possible solution too, but one caveat is that one
apparently has to live without referential integrity (at least at
the engine level) with a solution that uses this technology.

Sharepoint is no replacement at all for sharing real data, either
over TS or via replication.

 

[aaron.kempf]

or of course; you could use a FREEWARE database engine called MSDE or
SQL express.. and still use the forms and reports that you've already
developed

Access Data Projects are the best product to ever be released out of
Redmond.


-Aaron