I am trying to open a dbase5 table through ODBC and it will only open as read only....I have tried many different things to resolve this (many of the suggestions from here) but nothing seems to work. Anyone have any ideas?
Printable View
I am trying to open a dbase5 table through ODBC and it will only open as read only....I have tried many different things to resolve this (many of the suggestions from here) but nothing seems to work. Anyone have any ideas?
I don't know if this helps, but i've had a similar problem with Jet workspaces using adodc.connection objects. here are some of my solutions:
A) if you are using a dataenvinronment, change the properties of the connection object. there are two areas that set the read/write options. if you right-click on the connection object and click propertties and then click on the advanced tab, it will show you check-boxes to determine user access to the db. if you click on the all tab, there is also a place for the user permissions. THESE DON'T NECESSARILY MATCH UP.
B) also, opening a recordset, regardless of the specifications, doesn't override the connection properties if the connection is read-only. well, let me clarify. if the connection is read-only, then your recordsets will be read-only. if the connection is read/write, then your recordsets can still be read only if you specify. specifying a read/write recordset with a read-only connection will just be a pain in the, well, you know.
C) closing and terminating connections. if you are using a data environment to connect to a db, then thus far, any attemt to close the connection at the end of the first run doesn't really close it. it might say it's closed, but until you close and reload VB, the connection is still considered open. this means that if you try to connect, the system will see the database already being used by an administrator or someone, and will give you that error in some cases, in others it will just return the read-only error similar to what you're getting. if you're using the data environment, try doing it on the fly.
These have been some problems I've had that might help you out.
chuck
I had the same problem about a week ago. You can either read the thread about DBase III Tables or let me give you the quick way.
Instead of using the DBase driver, use the Foxpro ODBC driver. Otherwise install the Borland Database Engine. Both solutions work.
I was trying to do this in code. I threw a data control on the form and it works fine so I am just going to do it that way. thanks for the help.