Hi All:

Been a long time since last posting.

Have an ACCESS 2003 database of about 3500 records. Using VB2005, Im converting from ACCESS programing to VB. Have been successful in setting up a data screen with a a Binding Navigator to control movement throug the data retrieived with a SELECT Query. Only problem is when I try to modify data rows and save the modified data to the database using the SAVE button on the binding navigator. Code is as follows:

Try
Me.Validate()
Me.CONTLOGBindingSource.EndEdit()
Me.CONTLOGTableAdapter.Update(Me.KtplogDataSet.CONTLOG)
MsgBox("Update Successful")
Catch ex As Exception
MsgBox("Update Failed")
EndTry

After editing the data fileds and presing the SAVE button, I get the "Update Successful" message, the modified data does not show up in the database file. I checked the copy of the database file in debug folder of the application and find the changes are included in that copy. Yet, the changes are not in the main database file in the application.

Any suggestions on how to correct the situation?

Thanks in advance.

Greenbriar

Greenbriar,

You say that your database in the debug folder contains the changes that your app made but the main database does not. Are you trying to update two different databases?

I assume that you are using the data components in the toolbox. Make sure that your connection object is pointing to the database that you want to update.

Thearon

Theroon:

Tnx for the quick reply to my post.

Just prior to reading your post, I decided to try a reconfiguration by starting a new version of the application I'm developing. When developing the connection string, I got the screen asking if I wnated to copy my db file into the application folder. I responded 'yes' and then read the inforamtion describing the three conditions of the copy. It was then that I learned that what I was experiencing and described in my orginal post was stanadard, i.e., since I elected to copy the file 'always' and I was in the development phase, the changes I made to the db file would be copied to the db file in the debug folder of the application but not cared to db file in the level below it. As long as I was in the application development, the db file in the debug folder would be overwritten to reflect the original file. I have to admit it took a couple of readings of this to sink in and make sense to me. This means that what I thought was a problem was not a problem at all.

Greenbriar