system.mdw

  • Thread starter Thread starter LCalaway
  • Start date Start date
L

LCalaway

I have created a front end/back end scheme for a database to be shared by
two people on a very small peer to peer network. Security is not a
consideration, so, as I understand it, system.mdw can be used to implement
this scheme. If that is so, where is the best place to put the system.mdw
file? Is it necessary to create a "workgroup" under this plan over and
above merely attaching two front ends to one back end?

Thank you.
LCalaway
 
LCalaway said:
I have created a front end/back end scheme for a database to be shared by
two people on a very small peer to peer network. Security is not a
consideration, so, as I understand it, system.mdw can be used to implement
this scheme. If that is so, where is the best place to put the system.mdw
file? Is it necessary to create a "workgroup" under this plan over and
above merely attaching two front ends to one back end?
Click to expand...
If security hasn't been implemented then the default "system.mdw" file
native to each PC will suffice, you need do nothing in this respect. What
you must do though is to give each user their own copy of the front end.
Sharing single front ends amongst multiple users can lead to corruption.

Regards,
Keith.
www.keithwilby.com
 
Both users have XP Pro and Access 2002/2003. I created separate front ends
for the two users. There are three separate mdb files -- one back end and
two front ends. Each front end links to the back end tables. The back end
contains only tables. However, when we both try to access the "back end"
through our individual front ends at the same time, the last to access is
locked out. I have set all of the mdb files to "shared" with "no locks."

I created the databases without making any special work groups because I
didn't think that would be necessary if we were going to be relying on
system.mdw.

I would appreciate help to determine what else to check for my locked out
user.

Thank you

LCalaway
 
LCalaway said:
Both users have XP Pro and Access 2002/2003. I created separate front
ends for the two users. There are three separate mdb files -- one back
end and two front ends. Each front end links to the back end tables. The
back end contains only tables. However, when we both try to access the
"back end" through our individual front ends at the same time, the last to
access is locked out. I have set all of the mdb files to "shared" with
"no locks."
Click to expand...
Do all users have read/write/execute/delete NTFS file permissions to all
related folders?
 
Do your users have the ability to create files in the directory that
contains the backend? If not, Access cannot create an LDB file and opens
the database exclusively.
 
We are not using NTFS - but what would the answer be if one was NTFS and the
other was FAT.
 
With respect to sharing front-ends, my experience has been different. Where
I work we have what may be luxuries, an extremely fast and stable LAN and
well maintained PCs, and have been sharing the front-ends of 30 or so
applications without corruption issues. It makes most enhancement
deployments a snap.
 
You need to make sure that everyone who uses the mdb file has the
/Windows/ permissions necessary in order to create, open, read, update,
close, /and delete/, files in the folder where the mdb lives. This is
because Access needs those permissions in order to run & manage the
database.

HTH,
TC
 
Back
Top