S
segorese
Guest
This involves both forms and macros as best
as I can tell.
My main switchboard freezes up after running
a set of Run Macro commands successfully and sequentially within a "super" macro.
Simply running the
super macro from the Database window results in no errors. All of the individual macros
comprising the larger macro run just fine.
Each of the smaller macros have Add for
Data Mode and No for Save for each of the
queries they run. They are running a series
of file creation queries that first zap
and then recreate the files that were zapped.
Again, all the data looks as it should.
I've taken off all of the SetWarnings
and issue only only Echo=No command at
the beginning of the super macro.
All of the data is on a local PC. It has
been conjectured that my F-Prot virus software may have some role in this problem -- notably slowing down the processing time to such a rate that the user thinks that the program has frozen -- but I have turned it off and am still getting the error.
When trying to retrieve the "freeze" the
only function that will work is File>Exit,
and that only sometimes.
Has anyone run into this kind of problem before? Any suggestions if so?
Steve
Please respond to:
ses10@health.state.ny.us
as I can tell.
My main switchboard freezes up after running
a set of Run Macro commands successfully and sequentially within a "super" macro.
Simply running the
super macro from the Database window results in no errors. All of the individual macros
comprising the larger macro run just fine.
Each of the smaller macros have Add for
Data Mode and No for Save for each of the
queries they run. They are running a series
of file creation queries that first zap
and then recreate the files that were zapped.
Again, all the data looks as it should.
I've taken off all of the SetWarnings
and issue only only Echo=No command at
the beginning of the super macro.
All of the data is on a local PC. It has
been conjectured that my F-Prot virus software may have some role in this problem -- notably slowing down the processing time to such a rate that the user thinks that the program has frozen -- but I have turned it off and am still getting the error.
When trying to retrieve the "freeze" the
only function that will work is File>Exit,
and that only sometimes.
Has anyone run into this kind of problem before? Any suggestions if so?
Steve
Please respond to:
ses10@health.state.ny.us
