I have a rather maddening problem. Occassionally
my VB3 application pops up an Error #2004 during
some database manipulation. Typing out the error
message in the debug window with "print error(2004)"
gives me simply, "User-defined Error."
I have not defined any errors in my program. The
actual line where this is occurring looks like
db.Execute "UPDATE * FROM gtus SET New = False WHERE New = True"
where "db" is just an Access 1.1 database with
a table called "gtus" and an Integer field called
"New" that I want to set False for all records.
Seems like a pretty inocuous statement, eh?
How can a VB application generate an error that it
claims was defined by me??? All ideas/suggestions
welcome and appreciated.