set warnings autoexec

[bchi99]

Hi, i saved a autoexec macro to run and set warning messages to off. However, when i run a certain query, i still get an error message on data mismatches but i always click yes to make the query run and update the fields. Anyone know why the setwarnings to no isn't working?

[bchi99]

is it b.c the query is running on fields that are null?

[pbaldy]

For starters, I wouldn't set warnings off and leave them that way. More info here including a possible solution:

http://www.baldyweb.com/SQLWarnings.htm

[ssanfu]

I agree with Paul. I NEVER use "Set Warnings Off". I DO have a lot of error routines.

i still get an error message on data mismatches but i always click yes to make the query run and update the fields

I am curious why don't you fix the error? Handling errors by ignoring them is not good programming practice. If you get a low oil warning light in your car, do you just put a piece of tape over the light and ignore it?

[kagoodwin13]

I agree with Paul. I NEVER use "Set Warnings Off". I DO have a lot of error routines.


I am curious why don't you fix the error? Handling errors by ignoring them is not good programming practice. If you get a low oil warning light in your car, do you just put a piece of tape over the light and ignore it?

I use the "Set Warnings Off" code a lot for file imports/exports to and from Excel. Rather than confusing users with "Are you sure you want to add x number of rows to y table?" messages, I turn warnings off and have an "Import successful" vbOKOnly message at the end, and turn Warnings back on. I also use error trapping within the "Set Warnings Off/On" tags to handle any errors that may come up. A bit off topic, but there's a legitimate method of using the command.

bchi99, if you're having data mismatches, then I don't see how you are updating very well. Can you tell us more about what data you are trying to update? What is the source? What is the destination? How are the fields named? How are the fields formatted (for example, are you trying to put a date in a number field)?

[June7]

Use CurrentDb.Execute to run SQL actions and won't have to bother with SetWarnings.

[ssanfu]

Use CurrentDb.Execute to run SQL actions and won't have to bother with SetWarnings.

What I use.... plus it is faster - Currentdb.Execute is executed by Jet, Docmd.RunSQL is handled first by Access, then by Jet. (IIRC)