J
JIM
I have developed a database linked to SQL server 2000 in access97. When I
test the database on two of the three networks available to me, it will
allow multi-users to connect. But on one of those networks (the one where
the database is supposed to live) it will only allow one user at a time.
The database is not set for exclusive use and the security settings in
access appear normal. The folder in which the database resides is set for
full access for use by a user group set up specifically for this database.
This database was a standalone database which was accessible by more than
one user. I re-created it so it could be linked to the SQL Server. I think
it was originally done in access95 and converted to access97. When I
changed it, I started with Access97. I developed it on the server in
question using remote desktop.
This is not the only database I am having problems with on this server. It
seems that any database that is being converted for SQL Server acts the same
way. One in particular was converted from 2.0 to 95 to 97. Before
conversion it allowed multi-users, after it would not allow some users to
open it if it was already open, but it would allow others. This database was
developed offsite and moved to this server.
Some users are using PCs and others are using terminals to access the
database. Could the fact that there could be different versions of MDAC
being used cause this problem? Can anyone give me an idea of what may be
causing this problem?
test the database on two of the three networks available to me, it will
allow multi-users to connect. But on one of those networks (the one where
the database is supposed to live) it will only allow one user at a time.
The database is not set for exclusive use and the security settings in
access appear normal. The folder in which the database resides is set for
full access for use by a user group set up specifically for this database.
This database was a standalone database which was accessible by more than
one user. I re-created it so it could be linked to the SQL Server. I think
it was originally done in access95 and converted to access97. When I
changed it, I started with Access97. I developed it on the server in
question using remote desktop.
This is not the only database I am having problems with on this server. It
seems that any database that is being converted for SQL Server acts the same
way. One in particular was converted from 2.0 to 95 to 97. Before
conversion it allowed multi-users, after it would not allow some users to
open it if it was already open, but it would allow others. This database was
developed offsite and moved to this server.
Some users are using PCs and others are using terminals to access the
database. Could the fact that there could be different versions of MDAC
being used cause this problem? Can anyone give me an idea of what may be
causing this problem?