Msacces update queries not updating

One great place to find connection string data for tons of different databases is at

I am using a local instance of an access database that doesn’t require any real credentials to access. Ole Db namespace so we get to use Ole Db Connection as well as other classes you will see later.

So, with this simple query: “UPDATE Tbl Parameters SET Value=’1587′ WHERE Parameter=’Current Customer’;” You will get a “lock violation” if the Value field already contains “1587″.

If you’re doing this interactively, you can just click through the warning.

Create Object("ADODB.recordset") "Select Vch User Name, Vch Password, Bln Administrator from tbl User", conn do until rs.

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue.

So grab a drink, kick off your shoes and lets play with some snippets here on the Programming Underground!

msacces update queries not updating-57msacces update queries not updating-63

More information More information This error (HTTP 500 Internal Server Error) means that the website you are visiting had a server problem which prevented the webpage from displaying. So i tried to run it line by line so I figured out that the error is in the insert statement: sql="insert into tbl User Log (Vch User Name, Dte Logged, Vch Action)values ('" & duser & "','" & loggeddate & "','In')" conn.

All we need is to tell it which driver to use and where to find the database file. Then we give it the connection string and open the connection…

If this had been a database like My SQL located on another server, we would have to specify IP address info as well as port. Notice in our code above we create a new Ole Db Connection and give it a connection string to tells it where to find and to use our OLEDB 4.0 driver.

However, if you’re getting this problem in the middle of a program or script, all you need to do is to enclose the Update command within an if/then statement that checks to see if the value you want to update is already at the desired value. Yes, it’s one extra step, and one more hit on the DB, but that’s what you get for using Access as a front end.

With this in mind, a very common question in a variety of forums then becomes, how do we deploy a copy of the Front-End to our users and ensure that they always get any updates?


Leave a Reply