Ensuring SQL data is written

[Pete]

I have an application that is split (FE and BE). The FE always uses
SQL formatted strings to update records in the BE. Periodically the
data in the BE gets garbaged. It is always restricted to individual
records.

Some time times the system generated record number gets corrupted
along with other columns in the record.

I have never found the cause. I have been thinking that it might be
something assocated with some event on the users terminal (i.e. power
hit).

One thought is to "check' the acutal SQL command to ensure that data
has been properly written. Is this possible? Any other options
anyone can come up with.

the current code is generally as follows:

SQLstring = "UPDATE Roster SET " & SQLstring & " " & _
"Where RcdNumber=" & Me.tmpRcdNumber
End If

' Execute the SQL command
DoCmd.SetWarnings False
DoCmd.RunSQL SQLstring
DoCmd.SetWarnings True

 

[Jerry Whittle]

Fix what ever is causing the corruption.

Tony Toews has an excellent web page on database corruption.
http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:
http://www.rogersaccesslibrary.com/OtherLibraries.asp

 

[Pete]

Fix what ever is causing the corruption.

Tony Toews has an excellent web page on database corruption.http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database
towards the bottom this page:http://www.rogersaccesslibrary.com/OtherLibraries.asp
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.











- Show quoted text -

Already Looked at those items.