S
Steve
I have an Access application that launches overnight and basically takes
data several different sources and outputs a new combined tables.
My code is very easy and there is code present in only the Form_Open event
and I have startup options set to open my form:
Dim strsql as string
Dim db as database
Set db=currentdb
then repeat these next two lines in various forms about 20 times.
strsql="my sql code"
db.execute(strsql)
I am linked to roughly 35 tables and the sql statements pull, filter,
delete, append, and update tables so I end up with a few tables with my
desired information.
This all seems to work great except I seem to run into one issue
occassionally - I lauch this via task scheduler and I'll come in in the
morning and the program will be open with the following error:
"the Expression [OnLoad] "does not result in the name of a valid procedure
or macro."
If I close it out and do nothing but double click it a second time it runs
fine.
It takes a hour to process everything and I have run it manually 50 times
and never, ever encountered that error. It runs most nights with no issue,
but once a week it returns that error. Nothings changing in the program and
I can't seem to pinpoint the issue.
Anyone have any clues or tips?
thanks
data several different sources and outputs a new combined tables.
My code is very easy and there is code present in only the Form_Open event
and I have startup options set to open my form:
Dim strsql as string
Dim db as database
Set db=currentdb
then repeat these next two lines in various forms about 20 times.
strsql="my sql code"
db.execute(strsql)
I am linked to roughly 35 tables and the sql statements pull, filter,
delete, append, and update tables so I end up with a few tables with my
desired information.
This all seems to work great except I seem to run into one issue
occassionally - I lauch this via task scheduler and I'll come in in the
morning and the program will be open with the following error:
"the Expression [OnLoad] "does not result in the name of a valid procedure
or macro."
If I close it out and do nothing but double click it a second time it runs
fine.
It takes a hour to process everything and I have run it manually 50 times
and never, ever encountered that error. It runs most nights with no issue,
but once a week it returns that error. Nothings changing in the program and
I can't seem to pinpoint the issue.
Anyone have any clues or tips?
thanks