G
Guest
I have a form that opens on autostart. I added code for its OpenForm event,
and included the "On Error go to error-routine" command.
This code checks that a specific table has specific data in it. If it
doesn't, a message is displayed (OK only reply), after which the Quit command
executes.
Problem is: since I misspelled a column name for a column of that table, I
get a VBA error message. OK is the only response available, and when it is
made, the Quit command executes, and the mdb closes.
THE VBA ERROR TRIGGERS THE QUIT, SO I CAN'T GET BACK IN TO FIX THE ERROR
THAT TRIGGERS THE QUIT!
And, with Murphy's Law in effect, this is after 10 solid hours of intense
VBA coding.
So I tried correcting the misspelled column name that is causing the error,
by using NotePad. But even changing just one occurrence of one column name,
and saving the file with the mdb extension of course, Access doesn't
recognize the file. Access suggests that I repair & compact it. So I try to.
Access responds by saying that it doesn't recognize the file.
Over the gates of Hell, it is written (according to Dante): "Abandon all
hope, ye who enter here".
Is the situation hopeless, or does anyone out there know some way around
this self-inflicted injury?
Thanks.
and included the "On Error go to error-routine" command.
This code checks that a specific table has specific data in it. If it
doesn't, a message is displayed (OK only reply), after which the Quit command
executes.
Problem is: since I misspelled a column name for a column of that table, I
get a VBA error message. OK is the only response available, and when it is
made, the Quit command executes, and the mdb closes.
THE VBA ERROR TRIGGERS THE QUIT, SO I CAN'T GET BACK IN TO FIX THE ERROR
THAT TRIGGERS THE QUIT!
And, with Murphy's Law in effect, this is after 10 solid hours of intense
VBA coding.
So I tried correcting the misspelled column name that is causing the error,
by using NotePad. But even changing just one occurrence of one column name,
and saving the file with the mdb extension of course, Access doesn't
recognize the file. Access suggests that I repair & compact it. So I try to.
Access responds by saying that it doesn't recognize the file.
Over the gates of Hell, it is written (according to Dante): "Abandon all
hope, ye who enter here".
Is the situation hopeless, or does anyone out there know some way around
this self-inflicted injury?
Thanks.