Making use of Debug

[GraeagleBill]

I have a bug I'm trying to find where a table field is being erroneously changed. So far, I've not been able to spot the culprit stepping through the code. There are table queries, class modules as well as form modules where the bug might be found. It's not at all clear to me how to make use of "Watch" to find when a field is being changed. I.e., could be in an open recordset, SQL UPDATE SET, etc. I can't seem to get my brain wrapped around what I see on the subject via a Google search. I "think" what I want is for code to break when the value is changed, which would give me the opportunity to inspect the conditions under which the statement is executing.

A couple of hints here would be most helpful.
Thanks,
Bill

[June7]

Watch window is used to view changes to variables, not fields in table.

I have NEVER used it.

You have searched code for any references to that table/field?

A third party tool can search macros, queries, properties as well as code. I have used Rick Fisher's Find & Replace for Access. Cost about $50.

Other possibilities are VTools and MZTools.

[GraeagleBill]

Watch window is used to view changes to variables, not fields in table.

I was afraid that would be the answer, as that's all I could ferret out of what I found in my Google search.

I will try to do a better job of isolating the code path to step through its execution.

Thanks June,
Bill

[isladogs]

As well as searching for all VBA references to the field in the VB Editor, you can use Object Dependencies in Database Tools menu to search for all queries which reference the table concerned.
That still leaves macros for you to search manually

Otherwise, V-tools is free and works well.
For info, it seems Rick Fisher no longer updates his Find and Replace utility.
Not even sure he accepts payment for it either ... though someone may correct me on that.

[orange]

Bill, There are several free youtube videos related to debugging.

Here are a few
VBA - Debugging and Error Handling by Steve Bishop


The following by Access All In One:
VBA Debugging - Immediate Window - Microsoft Access Tutorial for Beginners by Access All In One
VBA Debugging - Watch Window - Microsoft Access Tutorial for Beginners

and more

Good luck.

[GraeagleBill]

I found that "little bugger". The troublesome field was getting erroneously changed in an UPDATE Query........ I had my single record hat on when I coded the UPDATE so the criteria expression was inappropriate.
Thanks June and Colin for your thoughts,
Bill