×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Checking if changes have been made to a MSAccess database

Checking if changes have been made to a MSAccess database

Checking if changes have been made to a MSAccess database

(OP)
My application provides the user the ability to add, edit or delete records from any of the many tables in an Access db. On exiting the app, I want to check if any changes have been made to the database. I have not yet found a way to do this-any ideas?

RE: Checking if changes have been made to a MSAccess database

If you are working in Access97, here's one way, using the 'Dirty' and 'OldValue' properties. If you're working with Access 2, you have to keep track of the data you are able to change, then make a DB call before you exit.


Sub UndoEdits()
If Me.Dirty Then
Me!btnUndo.Enabled = True ' Aktivera knappen.
Else
Me!btnUndo.Enabled = False ' Inaktivera knappen.
End If
End Sub

Sub btnUndo_Click()
Dim ctlC As Control
' För varje kontroll.
For Each ctlC in Me.Controls
If ctlC.ControlType = acTextBox Then
' Återställ gammalt värde.
ctlC.Value = ctlC.OldValue
End If
Next ctlC
End Sub

RE: Checking if changes have been made to a MSAccess database

(OP)
I am working with Access97, I do not know what you mean by 'Dirty' and 'OldValue' properties.

RE: Checking if changes have been made to a MSAccess database

The 'Dirty' and 'OldValue' properties apply to Access Forms. Since your question disdn't sepcify how you were modifyinbg your data, I chose q&d solution. If you are NOT using forms, plan B sez do like you'd do it in Access 2: Save the original values when you load the record into the application, then check the database for any change before you let the user leave. To be smart - save enough info so you can hit the record with a unique, indexed key (saves time), and since you are hitting multiple tables, use transactions, so you can roll back the whole schmear if anything goes BillGates.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login


Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close