Re: Programmatically connecting to backend
- From: "Albert D. Kallal" <PleaseNOOOsPAMmkallal@xxxxxxx>
- Date: Tue, 17 Apr 2007 12:34:57 -0600
It's almost as if the front end is now opening the back-end in
exclusive mode.
Has anyone seen this? Any suggestions? Server is Windows 2003, client
machines run Windows XP.
Yes, we see this a lot, and 99% of the time it means the users were not
given full permissions to that dir. when we say full permissions, that
include file create, file delete...full means full rights.
Ms-access is a simple file share, and when you go mulit-user, ms-access
attempts to create a locking file (the ldb file). This fie is used for
multi-user..and managing conflicts. If ms-access can't create this file,
then it opens the database in single user mode...
So, those users likely don't have full permissions to that directory, and
each user needs full rights..and that includes file create, and file delete
rights. When the user runs their front end, and opens the back end...a
locking file is created in the SAME directory as the back end file. (so,
users must be able to create and delete files in that directory).
--
Albert D. Kallal (Access MVP)
Edmonton, Alberta Canada
pleaseNOOSpamKallal@xxxxxxx
.
- References:
- Programmatically connecting to backend
- From: Rémi
- Programmatically connecting to backend
- Prev by Date: Re: Programmatically connecting to backend
- Next by Date: Re: Tab from Form Detail to Form Footer
- Previous by thread: Re: Programmatically connecting to backend
- Next by thread: Insert Into Runtime error
- Index(es):
Relevant Pages
|
