Access 97 databases changing to read only

[Casala]

I have an access 97 database solution that I have been re-distributing to multiple sites, some of these sites are able to log into the database but are un-able to update the data as it appears to be read only mode.
they have the same security as before and all databases associated with the product have the 'read only'check box in file properties turned off.
Many of these sites use a mixture of windows XP/2000/Win 98

Some of these sites have resolved the problem by re-installing Access 97 - but not all.
Does access have a problem if multiple windows versions are accessing it(98,2000, XP) and does it change the database to read only in these situations.

Please help,

 

[LesterTurtle]

Yes, this does happen if different versions of Access are being used to access the same database. You can correct this by putting all the tables in a separate, non-used database and having the user's database link back to the table database. Hope this helps.

 

[Casala]

Hi,
thanks so much for the reply,
All the users are using access 97 for this product. The data is in a different access 97 database to the forms/reports etc which link to the tables.
Where the difference is (that I can see) is the versions of windows that they are using, - (I could be on the complete wrong track here).
I am still trying to work out a consistancy here. Many of the sights have installed the module without any problems, but 5 sights have had these problems, where it makes the whole system as if you have read only rights.
- I am at a total loss. As I can't get the same problem on my setup.

 

[Casala]

Just a further comment, this problem has re-occured to a solution that has been stable for years and has just stopped working with the message "this record set is not updateable", The site is upgrading to windows XP.
Once the user in the XP environment logged into the access 97 solution, it has stopped it working in that environment.
When the database was copied back to a different network it ran fine from there???
unfortunatly this is completely out of my league,
please please, any help would be gratefully appreciated.

 

[LesterTurtle]

I'm not 100% positive, but I don't think Windows XP supports Office 97 applications. So, it might be helpful to either convert the database to a later version (2000 or XP) or move to a different version of Windows. This is definitely one of those fun parts of Microsoft - software incompatibility. Sorry...

Lesley

 

[psemianonymous]

What has changed: the user's computer or the file server? If you have changed servers, be sure your users have read/write permissions on the folder. If they don't, they can't edit the database.

--
Find common answers using Google Groups:

http://groups.google.com/groups?group=comp.databases.ms-access

Corrupt MDBs FAQ

http://www.granite.ab.ca/access/corruptmdbs.htm

 

[gilbertw]

This isn't limited to Access 97. I'm having the same problems with Access 2000 on XP.

I think it's to do with user permissions. If you log on as administrator to install the database and then log on as the user, they seem to be unable to use the database properly.

I'm getting round it at the moment by loggin on to the machine as the domain administrator and thenright clicking the .mdb file, choosing properties, security and then ticking full control.

When the user logs back on they don't get the read only messages. Not the best solutuion, but am looking into it some more.

 

[Casala]

Thankyou for that, I will pass this on to my more experiened helper. I am finding this really difficult to keep up with, I don't have XP and am now really nervous of all the potential problems that XP is going to generate when I do upgrade.
Please keep me in touch with any other clues you have, I truly appreciate your time.

thanks
Caroline