Y
yan
Hello,
Is anyone familiar with runtime? I installed a database on a computer with
Microsoft Access. I installed a copy on a computer with a runtime version of
Access; both computers are on a network (Novell). The backend is located on
the network drive. The 2 front-end are on the user's hard drive. The users
can't access the database at the same time. The copy on the runtime is a
read-only database with only a few forms (no reports)... the only use is to
find information. When the main user (with Microsoft access) tried to open
the main form, when it is in use by the other user, he received a debug
windows (... record not updatable).
When the main user is in the database, the 2nd user can't open any of the
forms.
The 2 databases are perfectly working on my own computers (peer-to-peer)
with one of the computer running the runtime version of access.
I verified the locking level in the 3 databases and the user rights on the
network drive.
Any idea how to fix this issue?
Thank you in advance for your time.
Annick Fransen
(e-mail address removed)
Is anyone familiar with runtime? I installed a database on a computer with
Microsoft Access. I installed a copy on a computer with a runtime version of
Access; both computers are on a network (Novell). The backend is located on
the network drive. The 2 front-end are on the user's hard drive. The users
can't access the database at the same time. The copy on the runtime is a
read-only database with only a few forms (no reports)... the only use is to
find information. When the main user (with Microsoft access) tried to open
the main form, when it is in use by the other user, he received a debug
windows (... record not updatable).
When the main user is in the database, the 2nd user can't open any of the
forms.
The 2 databases are perfectly working on my own computers (peer-to-peer)
with one of the computer running the runtime version of access.
I verified the locking level in the 3 databases and the user rights on the
network drive.
Any idea how to fix this issue?
Thank you in advance for your time.
Annick Fransen
(e-mail address removed)