C
Chuck
Just making another comment about the disappearing VBA code since I am the
original poster.
It continues to happen in our environment and it does indeed happen when
someone attempts to open the MDB or ACCDB file prior to the network drives
being mapped. We have tested this over and over and it occurs every time.
I just don't understand if you open a shortcut on your desktop to a MDB or
ACCDB file on a network drive and it isn't mapped yet, how the heck does
Access start and not return a file not found error. I've test this several
times and it attempts to open the database. Once that happens, the code is
corrupted.
We cannot split the database and put a front end on each desktop. No matter
what argument you have here in the group about that being the correct way,
as a military organization, that will not happen. I have tried to split the
database and still put the backend on a different drive, but it still the
VBA code gets deleted if the user opens the file prior to a complete map.
We have added a small script that will check for the existence of the map
drive and they are always the same assigned letters. The ability to
disconnect and re-map drives are disabled for the users in policies. No one
can add any hardware or put in USB drives because it will not be
recogonized. It is indeed a very tight sytem for the end user.
If the user runs the script, we have no problems with the code.
Unfortunately, I cannot stop someone from making a shortcut to the files.
I think at this point it is realized that the problem occurs, it is now a
matter whether or not Microsoft will look into it and see what the problem
is or how to prevent code from disappearing.
Thanks to everyone who made suggestions here.
original poster.
It continues to happen in our environment and it does indeed happen when
someone attempts to open the MDB or ACCDB file prior to the network drives
being mapped. We have tested this over and over and it occurs every time.
I just don't understand if you open a shortcut on your desktop to a MDB or
ACCDB file on a network drive and it isn't mapped yet, how the heck does
Access start and not return a file not found error. I've test this several
times and it attempts to open the database. Once that happens, the code is
corrupted.
We cannot split the database and put a front end on each desktop. No matter
what argument you have here in the group about that being the correct way,
as a military organization, that will not happen. I have tried to split the
database and still put the backend on a different drive, but it still the
VBA code gets deleted if the user opens the file prior to a complete map.
We have added a small script that will check for the existence of the map
drive and they are always the same assigned letters. The ability to
disconnect and re-map drives are disabled for the users in policies. No one
can add any hardware or put in USB drives because it will not be
recogonized. It is indeed a very tight sytem for the end user.
If the user runs the script, we have no problems with the code.
Unfortunately, I cannot stop someone from making a shortcut to the files.
I think at this point it is realized that the problem occurs, it is now a
matter whether or not Microsoft will look into it and see what the problem
is or how to prevent code from disappearing.
Thanks to everyone who made suggestions here.