L
Leslie Isaacs
Hello All
I have a split Access2K mdb, with a backend on a server and a frontend on
each of 5 PCs. I routinely work on a 'master' version of the frontend, which
also lives on the server and which is copied to each PC when it is booted up
in the morning. The frontend includes a 3rd party add-in application, which
requires some .ini files to be in place on the local workstation, and some
references to be set. Everything works fine, except that some of the PCs
don't seem to retain these references: immediately after each boot-up these
references are either unticked, or they are ticked but annotated as MISSING.
Then they have to be re-selected, and all if fine again ... until the next
boot-up.
This behaviour seems not to be consistent, either across all the PCs or even
for a given PC - or at least I have not been able to identify any rule that
will predict when the references will be retained and when they will not.
Anyone any ideas?
Hope someone can help.
Many thanks
Leslie Isaacs
I have a split Access2K mdb, with a backend on a server and a frontend on
each of 5 PCs. I routinely work on a 'master' version of the frontend, which
also lives on the server and which is copied to each PC when it is booted up
in the morning. The frontend includes a 3rd party add-in application, which
requires some .ini files to be in place on the local workstation, and some
references to be set. Everything works fine, except that some of the PCs
don't seem to retain these references: immediately after each boot-up these
references are either unticked, or they are ticked but annotated as MISSING.
Then they have to be re-selected, and all if fine again ... until the next
boot-up.
This behaviour seems not to be consistent, either across all the PCs or even
for a given PC - or at least I have not been able to identify any rule that
will predict when the references will be retained and when they will not.
Anyone any ideas?
Hope someone can help.
Many thanks
Leslie Isaacs