L
larrylard
Hello,
I have a very strange problem. I have inherited three .mdb files which
have the peculiar property that if any one of them is open in Access,
and any other of them is activated from Windows Explorer, no new
instance of Access is opened: instead the existing instance is switched
to, with no change in database.
Access behaves correctly with any other databases. Also, if these
'problem' databases are copied to another directory, their copies
behave correctly.
Things to do with related problems I have checked:
- My File Type Associations / Open With stuff is all correct (as
witnessed by Access behaving as expected with other databases)
- I don't have any dialogs open while attempting to switch from one
problem database to another
Things that might be relevant:
- All the problem databases are password protected (but note above that
when copied to a different directory, they behave correctly)
- There are linked table references between the problem databases (T
and L both link to tables in A) - but when I create the same
relationships in new databases, all is well
As I said, I have inherited these databases so I can only assume that
some arcane setting somewhere is causing this problem. Any insights
much appreciated...
I have a very strange problem. I have inherited three .mdb files which
have the peculiar property that if any one of them is open in Access,
and any other of them is activated from Windows Explorer, no new
instance of Access is opened: instead the existing instance is switched
to, with no change in database.
Access behaves correctly with any other databases. Also, if these
'problem' databases are copied to another directory, their copies
behave correctly.
Things to do with related problems I have checked:
- My File Type Associations / Open With stuff is all correct (as
witnessed by Access behaving as expected with other databases)
- I don't have any dialogs open while attempting to switch from one
problem database to another
Things that might be relevant:
- All the problem databases are password protected (but note above that
when copied to a different directory, they behave correctly)
- There are linked table references between the problem databases (T
and L both link to tables in A) - but when I create the same
relationships in new databases, all is well
As I said, I have inherited these databases so I can only assume that
some arcane setting somewhere is causing this problem. Any insights
much appreciated...