Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Shaun E on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

database cant be updated since move to new server

Status
Not open for further replies.

pms18066

Programmer
Jan 12, 2005
94
US
I have moved a database access 2003 to a new server. I access this through an application written in vb 6.0. The users were using a local copy of this database on the C drive of their laptops. I created a new odbc connection pointing to the dbase on the network S: drive. I can read data into my forms but cant do any updates. Get "must use updateable query". At first I thought it was cause my S: drive was read only. Changed all of that and still no luck...same error..
Is there something special I have to do when using access from a network drive.
 
what is the connection type?
and how are you trying to update your db? recordsets/direct sql statements

--------------------
Procrastinate Now!
 
I am using an odbc MS ACCESS connection. I am using direct sql statements to do the updates...

I have several distinct functions which do selects and updates to each table. Very simple system which worked fine locally for the last two years...

Once I moved it no more updating..
 

Your users should have Read Write Execute and Delete on the folder containing the database. Not only on the database file. That goes also for the folder where .mdw resides. Even for the default one without userlevel security!
 
The machine where the mdb file resides is not a "server". It is just a node of the workgroup. Is this a problem? everything I read seems to put a shared access database on a machine acting as a server...

The read write delete permissions are all set for the only user on the box - ADMIN.

The only user is ADMIN.

I have mapped this machine and logged on using admin as userid.

I can open up the database file in Access without getting the read-only messsage. But the application still looks at it as read only.

When the app uses odbc to connect to the datasource, how does the app pass along a userid to connect to the drive where the dbase is stored?? I am not passing anything in my code to do this so there must be some default processing that Jet does? Right?

Thanks
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top