Database keeps getting corrupted

[Guest]

I have a very simple database. It is split, with one form that runs off of
their desktop and a backend sitting on the network drive. For some reason, I
keep getting errors where the backend becomes an "unrecognized format". Then
to open the backend and repair becomes a nightmare. Anyone have any idea why
it would keep getting corrupted? There is only one form, a couple of tables.


Thanks

Nathan

 

[Wayne Morgan]

This is usually one of 3 things.

1) The Office and Jet patches aren't up to date on the computers that have
the front-end.
http://msdn.microsoft.com/data/downloads/updates/default.aspx
http://office.microsoft.com/en-us/officeupdate/default.aspx

2) The users aren't shutting down the front-end properly or it is crashing.

3) There is a problem with the network connection. This is the most likely
problem. If you're using a wireless network, the chance of the network being
a problem increases. Check to see if the problem only occurs when one
particular computer with the front-end is using the database. Also, make
sure that you have battery backups on the server, workstations, and all
hubs, routers, etc. A momentary power bump to a hub can easily corrupt the
back-end file if a front-end was trying to write to the file as the power
bump occurred. You may not even notice a flicker in the room lights and
still have this problem.

 

[Guest]

Thanks, I think your idea about it being the network is probably correct. We
seem to have a lot of problems with the WAN part of the network.

Thanks.

I do have it tracking users too, though just in case. I know we don't have
anyone going into via wireless.

 

[Wayne Morgan]

If you're using a WAN, you may be better off using remote control software.
This type of software allows the user to logon to a local computer and
remotely control it. This would keep the database running on the internal
network only. There are several options, among them is Microsoft Terminal
Services and Citrix Winframe (I think that's the name). Another option would
be to set up the database using web pages on a local web server. This would
probably require a lot of work and someone who knows web programming to have
it do what you want. Again, the advantage is that the web server would be on
the local network and therefore shouldn't have the problems accessing the
data file.