Problem getting database to work on other PCs

[Guest]

Hi. I have a couple of databases that I'm creating for some other people in
the office, and everything works fine as long as I run the DB from my PC. But
as soon as I try to run it from their PC, I get the message "Can't update.
Object is read only." Both of these DB's import text files off a network
drive as part of their primary function (they import a file, add some numbers
up, format the file correctly for uploading to our mainframe, then export the
data). I don't understand the holdup, none of my other DB's have been doing
this to anyone. Any ideas?

 

[Wayne Morgan]

Have you added Access Security to the db's? Where are the db's located, on
the local drive or a network share? If on a network share, what are the
user's permission on the share? If the share is on an NTFS drive, what are
the user's permissions in the NTFS? How many users are accessing the same db
file?

 

[Guest]

Have you added Access Security to the db's? No.

Where are the db's located, on the local drive or a network share?

I have put them on network drives and on local drives, both with the same
result.

If on a network share, what are the user's permission on the share?

We all have the same permissions on the network drive for our department, we
have full access to all but 4 or 5 directories. I can run the database off
the network drive perfectly fine, but nobody else can.

How many users are accessing the same db file?

Just one at a time.

Hope that helps clarify things.

 

[Wayne Morgan]

In that case, could the problem be with access to the text files you're
importing or the location you're exporting to when you're done? How did you
copy the file to the other computers? If you used a CD or other type of read
only device, the read only attribute may have gotten copied along with the
file. If so, you'll need to right click the file in Explorer, choose
Properties, and clear the Read Only attribute.

 

[Guest]

I'll have to check on that again, I checked the database through Access, but
it didn't show any read-only attributes. I forgot to look at the actual .mdb
in Explorer, lol. I guess that will have to wait until Monday.