EXCLUSIVE ACCESS

[Andre Laplume via AccessMonster.com]

Here is a strange one. Many times I need to be in a db along with someone
else. (We use our dbs to simply extract data from various systems) Every
now and then we hit a db where only one person can be in it at a time. We
never could figure out why because the db is set to shared access (Tools
Options Advanced)

These are inheted dbs from a creator long gone. What event could override
the apparent SHARED access of a db and make it EXCLUSIVE. I see no modules
anywhere that might be executed on-open.


THANKS!!!!!

--
OOPs a typo...the statement that DOES NOT work is:

AdjAmt: Sum(IIf([TYPE]=2 And Left(Date(),2)="07",[Amt]*[Percent],IIf([TYPE]=1,

[Amt]*[Percent],0)))

Message posted via AccessMonster.com

 

[Douglas J. Steele]

Do all the users involved have sufficient permissions on the folder in which
the MDB file resides? All users must have Read, Write, eXecute and Delete,
or you'll run into problems like what you're seeing.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

Here is a strange one. Many times I need to be in a db along with someone
else. (We use our dbs to simply extract data from various systems) Every
now and then we hit a db where only one person can be in it at a time. We
never could figure out why because the db is set to shared access (Tools
Options Advanced)

These are inheted dbs from a creator long gone. What event could override
the apparent SHARED access of a db and make it EXCLUSIVE. I see no modules
anywhere that might be executed on-open.


THANKS!!!!!

--
OOPs a typo...the statement that DOES NOT work is:

AdjAmt: Sum(IIf([TYPE]=2 And
Left(Date(),2)="07",[Amt]*[Percent],IIf([TYPE]=1,

[Amt]*[Percent],0)))

Message posted via AccessMonster.com

 

[HERE IS WHY via AccessMonster.com]

Yes we all do.

It is very strange. I have been toying with the idea of emptying a non -
affected db and re-filling it with all the tables, queries etc from an
affected one and see if that solves the problem. Still I can not help but
think (hope?) there was a simple setting or something somewhere.

Thanks!

Do all the users involved have sufficient permissions on the folder in which
the MDB file resides? All users must have Read, Write, eXecute and Delete,
or you'll run into problems like what you're seeing.

Here is a strange one. Many times I need to be in a db along with someone
else. (We use our dbs to simply extract data from various systems) Every

[quoted text clipped - 9 lines]

[Amt]*[Percent],0)))

 

[TC]

Just a thought, 'cos I haven't personally tested this:

As well as checking what Douglas said (all uses must have
read/write/create/delete/open/whatever-else-you-can-think-of
permissions on the folder where the database is, make sure that they
also have the same permissions on the folder where the /worgroup
information file/ is.

To find the workgroup information file, open the db then look for an
open file with extension .LDB. Then close the db & see if that LDB file
disappears. If so, that's the folder you want; check its permissions.

HTH,
TC

 

[HERE IS WHY via AccessMonster.com]

Let me give a specific example. I open db1. My buddy opens db1....it lets
her in but in read-only mode. When I look in EXPLORER I see two files: db1.
mdb and db1.ldb. We close everything.

I open db2. My buddy opens db2....it tells her the db is open exclusively
and will not let her in, When I look in EXPLORER I see only ONE file: db2.
mdb...I see no ldb file.


There is some fundamental setting difference between the two dbs that causes
db2 to open EXCLUSIVELY.

What could it be?

 

[SOLUTION--maybe via AccessMonster.com]

I am not claiming this makes any sense but....

I went to exporer and drilled may way to the folder that houses our dbs. I
went to properties. Under: Attributes, ReadOnly was greyed out with a check
mark. I clicked it. The box lit up with nothing in it. I clicked: APPLY.
I clicked: OK when asked if it should be applied to all files/subfolder there
in.

Now when more than one person opens those previously 'always' exclusive dbs,
they open shared and I see the .ldb file.

Like I said I am unsure if this makes sense or not but part of my problem
appears to be resolved.

Let me give a specific example. I open db1. My buddy opens db1....it lets
her in but in read-only mode. When I look in EXPLORER I see two files: db1.
mdb and db1.ldb. We close everything.

I open db2. My buddy opens db2....it tells her the db is open exclusively
and will not let her in, When I look in EXPLORER I see only ONE file: db2.
mdb...I see no ldb file.

There is some fundamental setting difference between the two dbs that causes
db2 to open EXCLUSIVELY.

What could it be?

Just a thought, 'cos I haven't personally tested this:

[quoted text clipped - 10 lines]

HTH,
TC

 

[TC]

Douglas and I have both been telling you to check the relevant folder
permissions, but it seems that you have only just done so!

TC

 

[SOLUTION--maybe via AccessMonster.com]

Well, the change I made in actuality should have changed nothing since it
showed the access all along, still the act of clicking and applying evedently
did.