VBA code appears to call a another code but it doesn't actually run

[cinstanl]

I have a workbook that is connected through an ODBC to web program. Part of the code is supposed to match an invoice from one worksheet to an invoice on another and then add data to it. It is called by a another set of codes... it does not error out and it actually triggers the clear content section, it does not error out, it appears that it is updating the information but it is not really updated... if I walk through the code by pressing F8, it updates with accurate data. This is the code that I am using, I know the code works from beginning to end as long as I press F8 to get through it.. but there is over 700 rows that I am manually looping through... Can someone look at this code and see if there is something that is obvious to you that I am not seeing. Why would it work manually pressing F8 but not actually update when selecting Run?

Please Login or Register  to view this content.

[Richard Buttrey]

Hi,

It's rather difficult to say without seeing the code in the context of the whole workbook. Sometimes when stepping through code it's easy to start with the wrong Active sheet'. When you step through is the active sheet the same sheet that presumably contains the 'Run' button?

I see that DC isn't dimmed but maybe you don't have 'Option Explicit' at the top of your code and if so this point is irrelevant.

Have you tried putting a break point in and then Running the code from the button and starting the code in VBA with the F5 key. Check to see that they both get to the breakpoint, and if so move the breakpoint further to see if you can establish where the difference occurs. You may need to use the WATCH window and set a Break for the Loop section.

Upload the workbook if you still struggle.

[cinstanl]

Thank you for the response... I thought about putting a break in and watch it, but it runs if you F8 through it, so I did not think that putting a break in it would tell me anything... when you run the code, automatically, it gives you the impression that it is running the entire code, but it is clearly not, it only puts the accurate date in the appropriate cells when I F8 through it. I will try and get the file attached, but I think it might be to big..the thing is, when anyone selects Refresh, it will ask for a password because the SQL tables that are linked through an ODBC file. So the refresh part will not work for you when testing it.

[cinstanl]

When testing it, I know it is not working when I filter the vendor and see that there is project data in column V, when I filter out everyone but Vernovis, Vernocvis should always be blank...

[Richard Buttrey]

I suggested a break since you say the F8 runs all the way through, but running the macro, from a button presumably, doesn't.
Hence a technique I often use is to identify exactly where the difference occurs. It's trial and error but you can usually hone it down by halving the code lines/loop iterations for each test. You're looking to find the position where the break STOPS occurring in both the F8 and Run scenarios.

[cinstanl]

Thanks, I tried the break, but could not determine why its breaking. I did add another button and assigned the MatchInv code to it. It works this way, but you have to push 3 buttons to get everything that you need. I guess we will just deal with pressing 3 buttons.