R
Rob Rohrbough
I will be preparing to run some of my clients' Access 2000
databases under Access 2002. Tested the first one this
AM. Was able to open the DB OK. Was able to execute the
startup macro manually until I tried to open a module -
just to view the code, not change it.
The first messages I saw said, "You must have Visual
SourceSafe version 6.0 or later installed to run the VBA
Source Code Control Add-In." I do not intend to use/have
not used VSS. After clicking OK several times (same
message), it launched the VBA editor. I closed it without
making any changes, but, when I tried to run the macro, I
recieved the message, "Can't find project or library."
Only when I deleted that copy of the DB and copied my
backup was I able to get the macro to run again.
Is this expected behavior? Workarounds? Fixes (e.g., in
Service Releases?
TIA,
Rob
PS: See my related post, "Acc10 cannot run the /X command
on Acc9 DB".
databases under Access 2002. Tested the first one this
AM. Was able to open the DB OK. Was able to execute the
startup macro manually until I tried to open a module -
just to view the code, not change it.
The first messages I saw said, "You must have Visual
SourceSafe version 6.0 or later installed to run the VBA
Source Code Control Add-In." I do not intend to use/have
not used VSS. After clicking OK several times (same
message), it launched the VBA editor. I closed it without
making any changes, but, when I tried to run the macro, I
recieved the message, "Can't find project or library."
Only when I deleted that copy of the DB and copied my
backup was I able to get the macro to run again.
Is this expected behavior? Workarounds? Fixes (e.g., in
Service Releases?
TIA,
Rob
PS: See my related post, "Acc10 cannot run the /X command
on Acc9 DB".