Have a working Database, just can't share it.

[Dave]

Have a working Database, just can't share it.

I have build a database to track cats for our adoption
clinic. It tracks when they come in and when they were
adopted out, as well as some memo fields. During
development we have a lab with 4 pc's, 2 running XP pro
sp1, 1 2k no sp, one XP home full updated. In the lab we
have no firewalls running and are using TCP/IP networking,
all machines have office 2000 (only the 2k machine has the
Office1a and SP3 updates currently). After development
this database will be hosted on the domain. The goal is
to allow multiple users access to the same table,
interacting with only one record.
The current problem is sharing the Database, on
the LAN, and on the local machine. I did read through the
help file and tried all the settings it recommended to no
avail. In tools/options/advanced I have the database set
to open as shared. For record locking I have tired all
options; no locks, all records, edit records. As well as
checking and un-checking 'open database using record level
locking'.
For a first test we put the database in a shared
folder, we could open it locally, but when LAN pc tried to
open the database we received the error message 'could not
lock file'. It did not seem to mater what pc we shared
the Database from all results were the same. Also worth
noting, if the local user closed the Database the Network
User could open the Database.

Next we configured users and groups. On the local
machine multiple users could open the Database. But when
more then one user opens the primary table that index's
the cats Id number, the whole table gets locked down, not
just the current record in use. Other users are then
locked from the table and receive this error
message 'could not lock table "table name"; currently in
use by user "user name" on machine "machine name"'. After
the users and groups where created no LAN user could open
the database the error message 'could not lock file'.
This also happened when no other users had the Database
open.

Closing notes questions. First am I correct that I
should be able to share the Database with a small group of
users who all interact with the same primary table? Or
should this be more of a run time application? Or am I
completely off base, and will need to build a Front Page
interface front end? I figured the less complicated the
better, look at the problems I am having with Access lol.
Any advice?? Anyone? I looked through the knowledge base
but must be using the wrong key terms, I'll take any
help..

Thanks,
Dave

 

[Guest]

Mike,
Things to Check:
- In the backend database, Check under tools, options:
under advanced tab, check "Shared" and "No Locks"
- XP can be tricky in regard to sharing files. If you
use "Simple File Sharing" under folder options, then make
sure that both the "Share this file" and "Allow Network
users to change my files" are checked off under the
properties for the folder you are sharing. If you don't
use simple file sharing, then all users must have, modify,
read, write permissions on that particular folder.
Also, I have noticed that after compacting and repairing a
databse in a shared folder on XP, it can be come
inaccessable to remote clients. You need to copy the file
to a new folder, and share that folder.
Hope that helps

 

[Tom Wickerath]

If you don't use simple file sharing, then all users must have

modify, read, write permissions on that particular folder.

Actually, all users DO need RWCD privileges for the shared folder. Simple file sharing
will not suffice.

See Introduction to .ldb Files
http://support.microsoft.com/?id=208778

Tom
__________________________________


Mike,
Things to Check:
- In the backend database, Check under tools, options:
under advanced tab, check "Shared" and "No Locks"
- XP can be tricky in regard to sharing files. If you
use "Simple File Sharing" under folder options, then make
sure that both the "Share this file" and "Allow Network
users to change my files" are checked off under the
properties for the folder you are sharing. If you don't
use simple file sharing, then all users must have, modify,
read, write permissions on that particular folder.
Also, I have noticed that after compacting and repairing a
databse in a shared folder on XP, it can be come
inaccessable to remote clients. You need to copy the file
to a new folder, and share that folder.
Hope that helps

__________________________________


Have a working Database, just can't share it.

I have build a database to track cats for our adoption
clinic. It tracks when they come in and when they were
adopted out, as well as some memo fields. During
development we have a lab with 4 pc's, 2 running XP pro
sp1, 1 2k no sp, one XP home full updated. In the lab we
have no firewalls running and are using TCP/IP networking,
all machines have office 2000 (only the 2k machine has the
Office1a and SP3 updates currently). After development
this database will be hosted on the domain. The goal is
to allow multiple users access to the same table,
interacting with only one record.
The current problem is sharing the Database, on
the LAN, and on the local machine. I did read through the
help file and tried all the settings it recommended to no
avail. In tools/options/advanced I have the database set
to open as shared. For record locking I have tired all
options; no locks, all records, edit records. As well as
checking and un-checking 'open database using record level
locking'.
For a first test we put the database in a shared
folder, we could open it locally, but when LAN pc tried to
open the database we received the error message 'could not
lock file'. It did not seem to mater what pc we shared
the Database from all results were the same. Also worth
noting, if the local user closed the Database the Network
User could open the Database.

Next we configured users and groups. On the local
machine multiple users could open the Database. But when
more then one user opens the primary table that index's
the cats Id number, the whole table gets locked down, not
just the current record in use. Other users are then
locked from the table and receive this error
message 'could not lock table "table name"; currently in
use by user "user name" on machine "machine name"'. After
the users and groups where created no LAN user could open
the database the error message 'could not lock file'.
This also happened when no other users had the Database
open.

Closing notes questions. First am I correct that I
should be able to share the Database with a small group of
users who all interact with the same primary table? Or
should this be more of a run time application? Or am I
completely off base, and will need to build a Front Page
interface front end? I figured the less complicated the
better, look at the problems I am having with Access lol.
Any advice?? Anyone? I looked through the knowledge base
but must be using the wrong key terms, I'll take any
help..

Thanks,
Dave

 

[Tom Wickerath]

During development we have a lab with 4 pc's, 2 running

XP pro sp1, 1 2k no sp, one XP home full updated.

If you don't want to run into some serious problems, I strongly advise you to patch the 2k
install that has no sp. Otherwise, you'll end up posting another issue to us:

Error Accessing File. Network Connection May Have Been Lost.
http://support.microsoft.com/?id=304548


Tom
__________________________________________

Have a working Database, just can't share it.

I have build a database to track cats for our adoption
clinic. It tracks when they come in and when they were
adopted out, as well as some memo fields. During
development we have a lab with 4 pc's, 2 running XP pro
sp1, 1 2k no sp, one XP home full updated. In the lab we
have no firewalls running and are using TCP/IP networking,
all machines have office 2000 (only the 2k machine has the
Office1a and SP3 updates currently). After development
this database will be hosted on the domain. The goal is
to allow multiple users access to the same table,
interacting with only one record.
The current problem is sharing the Database, on
the LAN, and on the local machine. I did read through the
help file and tried all the settings it recommended to no
avail. In tools/options/advanced I have the database set
to open as shared. For record locking I have tired all
options; no locks, all records, edit records. As well as
checking and un-checking 'open database using record level
locking'.
For a first test we put the database in a shared
folder, we could open it locally, but when LAN pc tried to
open the database we received the error message 'could not
lock file'. It did not seem to mater what pc we shared
the Database from all results were the same. Also worth
noting, if the local user closed the Database the Network
User could open the Database.

Next we configured users and groups. On the local
machine multiple users could open the Database. But when
more then one user opens the primary table that index's
the cats Id number, the whole table gets locked down, not
just the current record in use. Other users are then
locked from the table and receive this error
message 'could not lock table "table name"; currently in
use by user "user name" on machine "machine name"'. After
the users and groups where created no LAN user could open
the database the error message 'could not lock file'.
This also happened when no other users had the Database
open.

Closing notes questions. First am I correct that I
should be able to share the Database with a small group of
users who all interact with the same primary table? Or
should this be more of a run time application? Or am I
completely off base, and will need to build a Front Page
interface front end? I figured the less complicated the
better, look at the problems I am having with Access lol.
Any advice?? Anyone? I looked through the knowledge base
but must be using the wrong key terms, I'll take any
help..

Thanks,
Dave