I had this same problem when Vista first came out, and now it appears
to be rearing its ugly head again.

If I open an Access database that is located on a network drive
(Windows 2003 server), and even open a module to look at the VBA code,
when I close the database, it corrupts it. I lose all modules, forms
etc...

Same database, if I copy it locally first, I can open and change code
at will, then move it back to the network and all is well.

Pretty much identical to the issue in Vista (http://
support.microsoft.com/kb/935366/).

Has anyone else seen this? If so, any solutions?

Tim

Dagills22191 <(E-Mail Removed)> wrote in
news:1094b9e9-96b7-45e6-9198-(E-Mail Removed)
:

> I had this same problem when Vista first came out, and now it
> appears to be rearing its ugly head again.
>
> If I open an Access database that is located on a network drive
> (Windows 2003 server), and even open a module to look at the VBA
> code, when I close the database, it corrupts it. I lose all
> modules, forms etc...
>
> Same database, if I copy it locally first, I can open and change
> code at will, then move it back to the network and all is well.
>
> Pretty much identical to the issue in Vista (http://
> support.microsoft.com/kb/935366/).
>
> Has anyone else seen this? If so, any solutions?

Does the hotfix fix the problem?

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/