jet db on linux file server problems

  • Thread starter Thread starter Keith G Hicks
  • Start date Start date
K

Keith G Hicks

One of my clients moved the backend of the Access app that I wrote for them
onto a Linux server a couple of years ago. I don't know a lot about how they
are handling that since I'm not familiar with Linux. The front end mdb of
course is runnig on all Windows machines. When they first set it up they
were very pleased (and mostly still are). The server runs great and the
speed is much better than what they used to have. But early on in running
things we noticed occasional (every few months or so) corruption that I've
never seen with my clients that run all their Access apps on purely Windows
systems. Records would become corrupt and sometimes indexes would get blown
away which would in turn blow away relationships between some tables. More
recently for some reason the entire backend mdb got fried. Fortunately they
are diligent about doing backups and installed one from the day before.

I've done a little bit of hunting on line to see if there's a common problem
out there when using Access and Linux and what the solution might be but I'm
not getting very many results. Has anyone experienced this and if so is
there a good solution? (other than changing from Linux to Windows which
they're not going to do).

Thanks in advance,

Keith
 
You should turn off opportunistic locking and
file caching on both the server and on the clients.

At the server end, this might be something simple
like marking the file as 'shared', or it might be
something complex and obscure.

At the Windows Client side, it depends on the version
of Windows. Perhaps something like this:


Configuring opportunistic locking in Windows
http://support.microsoft.com/?kbid=296264



However, Access is uniquely sensitive to network
errors: they might just have a dodgy network card,
hub, cable or driver.

Corrupt Microsoft Access MDB Causes
http://www.granite.ab.ca/access/corruption/causes.htm


(david)
 
Thanks to your suggestion, my client did do this a couple of weeks ago by
the way. Apparently things are just fine now. Thank you.

You should turn off opportunistic locking and
file caching on both the server and on the clients.

At the server end, this might be something simple
like marking the file as 'shared', or it might be
something complex and obscure.

At the Windows Client side, it depends on the version
of Windows. Perhaps something like this:


Configuring opportunistic locking in Windows
http://support.microsoft.com/?kbid=296264



However, Access is uniquely sensitive to network
errors: they might just have a dodgy network card,
hub, cable or driver.

Corrupt Microsoft Access MDB Causes
http://www.granite.ab.ca/access/corruption/causes.htm


(david)
 
Back
Top