G
Gargamil
I have an Access database which is used to interrogate and report on a set
of Paradox tables. When I try to open a table that is already open I get
the error 11265. This whilst being annoying I can live with knowing the
locking protocols for Paradox can be restrictive. C'est la vie.
The problem is that others get the same error EVERY time they open the
database. We've checked that no-one has them open but still the error
persists. For example, they will get the error, then I'll be able to open
it, I'll close down and they still get the error. One machine is an
identical setup - bought and configured at the same time. The same error
number is reported when the database is run under a Citrix client.
Can anyone shed some light on what might be going on here??
g
of Paradox tables. When I try to open a table that is already open I get
the error 11265. This whilst being annoying I can live with knowing the
locking protocols for Paradox can be restrictive. C'est la vie.
The problem is that others get the same error EVERY time they open the
database. We've checked that no-one has them open but still the error
persists. For example, they will get the error, then I'll be able to open
it, I'll close down and they still get the error. One machine is an
identical setup - bought and configured at the same time. The same error
number is reported when the database is run under a Citrix client.
Can anyone shed some light on what might be going on here??
g