jet db on linux file server problems
- From: "Keith G Hicks" <krh@xxxxxxxxxxx>
- Date: Tue, 12 Apr 2005 14:38:38 -0400
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
.
- Follow-Ups:
- Re: jet db on linux file server problems
- From: david epsom dot com dot au
- Re: jet db on linux file server problems
- Prev by Date: Re: How to Update a Destination Table using a Source Table using VBS
- Next by Date: Re: Exporting query forumula from Access 2000/2002
- Previous by thread: Automatic Scheduled Import
- Next by thread: Re: jet db on linux file server problems
- Index(es):
Relevant Pages
|
