mdb file (independent of path) is read-only on some machines

[Eric Johnson]

I've run into a situation in which one machine can do data entry on a
particular MDB, and others can't.

This doesn't appear to me to be a Windows domain or filesystem
permissions issue, because one can copy the DB the edit-capable machine
onto a memory stick (FAT32 rather than NTFS) and it _still_ will only
open when the stick is connected to the machine on which it works. Same
deal when the file is placed on a network drive.

The DB is Access2000 format, and the machine from which it can written
to is running Access2003. A machine on which the DB cannot be opened
except as read-only is running Access2000 (I don't know about other
machines on the network, as I'm 30 miles away without remote access)

I can open and edit an zipped/emailed copy of the DB and make edits in
my copy.

The machines in question are on a Windows domain (though my own machine
isn't on that domain -- or even that LAN), but as I mentioned, this
doesn't seem to me to be a network/filesystem permissions issue.

To my knowledge, there's no restrictive security stuff on the _inside_
of the MDB, based on just grabbing the thing and trying out some changes
to data and code on my machine, but I don't know enough to be sure.

Any thoughts on causes, solutions, or avenues for further inquiry?

Thanks!

Eric Johnson

 

[Guest]

The first release of A2000 had a different MDW than the
current release. In some rare conditions that might cause
problems. Obviously, not often, or everyone would know
about it. ?It had to do with the ?engine account ??. In any
case, it's easy to test - make a copy of the mdw in use, use
shortcuts to start Access so you can be sure, test it on both
machines.

Also, is it just this one mdb? Also, how big is this memory
stick? You need to try it on a drive (like a floppy) with a FAT
file system, not NTFS, because the FAT file system has fewer
and more obvious permissions.

(david)