I have been having a rather aggravating problem with databases
becoming corrupt after opening them on a Vista machine. I have finally
found a common theme to the problem, and a work around, and am
wondering if anyone else has had this problem.
Running Access 2003 on a Vista Business computer in a Windows 2003 AD
environment. If I open an Access database, make any changes to ANY
object, then close the database and allow it to automatically compact
itself, the database ends up corrupt and I can no longer open it under
Vista, nor under XP. I have found that if I turn off the automatic
compacting, I no longer have the problem. Further, this onnly occurs
to databases that are stored on network drives. If I first make a copy
of the database to a local drive, and modify that copy, it will NOT
become corrupt when it compacts.
Further, this wasn't an issue when I first switched to Vista. I used
it for about 2 months with no problem. The corruption began happening
after I installed the Office Compatability Pack about a week ago. I
tried uninstalling it, but the problem remains.
Tim
Arvin Meyer [MVP] - 26 Sep 2007 14:07 GMT
I suspect you have a bad network card somewhere between your machine and the
server. I can confirm that running on Vista with Access 2003 with Service
Pack 2 does not corrupt when the front-end is on the workstation, or during
the development when running entirely on the workstation, using Compact on
Close.
Under only very limited circumstances should you be running a front-end from
a server unless you are using Terminal Server. NEVER share a front-end.
There have been some reports of erratic behavior/bugs after SP3. I cannot
confirm any of those because SP3 is not installed yet on anything I use for
production.

Signature
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
>I have been having a rather aggravating problem with databases
> becoming corrupt after opening them on a Vista machine. I have finally
[quoted text clipped - 17 lines]
>
> Tim