Is there an issue with displaying a message box after if/end if statement in 2010 macro or do I have something in the wrong place? I think I have attached a picture of the macro order.
Is there an issue with displaying a message box after if/end if statement in 2010 macro or do I have something in the wrong place? I think I have attached a picture of the macro order.
Depends what happens within the If Then code. Is there maybe an Exit Macro? I don't use macros so not sure that is possible. Exiting a procedure before all code runs is possible in VBA.
Programmatically changing db design is usually a bad idea. Why are you importing data to new tables and not existing tables?
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
The IF command sends an email to a distribution list, if a query has any results. My intent was for the message box to run independent of the if statements, but that's not the case. Today was the first day that the message box appeared and it corresponded to it being the first day there were results to email. I assumed that the message box being listed after the end if would keep them apart, but that's not happening. Do I need another command between them so the message box fires regardless of the outcome of the IF commands?Depends what happens within the If Then code. Is there maybe an Exit Macro? I don't use macros so not sure that is possible. Exiting a procedure before all code runs is possible in VBA.
Programmatically changing db design is usually a bad idea. Why are you importing data to new tables and not existing tables?
Since I don't use macros, not sure. I would think the MsgBox should run regardless, it would in VBA.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.
Bump. I'll entertain any ideas at this point.
Syntax for the MsgBox arguments looks odd to me but I don't use macros and I have 2010. Maybe drop the last comma, but I would expect that extraneous comma to trigger error.
Could post db for analsyis. Follow instructions at bottom of my post.
Or convert macros to VBA and post VBA code for analysis.
How to attach file: http://www.accessforums.net/showthread.php?t=70301 To provide db: copy, remove confidential data, run compact & repair, zip w/Windows Compression.