SetWarnings Reversed - Convert Query SQL to VBA in Microsoft Access


	Back to Convert Query SQL to VBA Comments List

Upload Images @Reply Bookmark Link Email Next Unseen

SetWarnings Reversed

James Gray

5 years ago

I noticed that the VBA code constructed via the utility has the Set Warnings True statement first instead of Set Warning False. I think the problem is with the construction of Status function. I fixed it by changing the order of construction for StatusBox to: StatusBox = StatusBox & vbNewLine & S instead of: StatusBox = s & vbnewline & Statusbox. Do I have this correct?

	Richard Rost @Reply 5 years ago
You may indeed be correct. I didn't notice it. I'll check the video when I have some free time, but what you're saying sounds about right. Thanks. :)

	Scott Axton @Reply 5 years ago
I can confirm that this is the case. I just noticed it as well. It is because of how the string is written to StatusBox. The last command coming in at the top. It's difficult to see because in the vba code it is written correctly the way access would normally treat it. Set Warnings False DoStuff SetWarnings True Now read the same above from the bottom up

	Richard Rost @Reply 5 years ago
Silly me. :) Thanks.

	Justin Hull @Reply 4 years ago
I Noticed this too. Just found this the other day, thank you for this. this helps soooooo much. I just ended up swapping the true and false in the code under the form and it now puts it on the screen correctly

This thread is now CLOSED. If you wish to comment, start a NEW discussion in Convert Query SQL to VBA.

Next Unseen

New Feature: Comment Live View