Error Message after a successfull MS Access Macro Launch

microplan · Post by **microplan** » Sun Sep 12, 2004 1:28 pm

Hi - I'm new with MacroScheduler. Up to now I used another scheduler software, but I want more flexibility. Currently, I'm simply transporting the existing automated macros from the "old" scheduler to "Macro Scheduler". In principle, it works. However, there are some strange events / behaviors for which I have no explanation, for example:

When an MS Access job is started by MacroScheduler (I simply execute an MS Access mdb file which internally exeutes its own macros and then terminates) all things work fine. After successfull completion, MS Access terminates as expected. But some seconds later a message window (modal) appears which means that the desired file xyz.mdb could not be found. Because the icon of this window is the icon from MacroScheduler I assume that this is a MacroScheduler message although the Window header lines reads "MS Access". I have to manually click the window away.

What is the reason for such a message window (internal timing ?), how can I prevent it ? I logged the jog, but there are no errors reported. I already tried to step into the mdb files directory by a ChangeDirectory command of MacroSCheduler before executing the mdb file, because I assumed a file/path error, but this does not help.

Thanks,
Klaus

Lumumba · Post by **Lumumba** » Sun Sep 12, 2004 4:00 pm

Could you provide your code ?
Do you use Run Program> or Execute File> to run that *.mdb ?

Guest · Post by **Guest** » Mon Sep 13, 2004 9:39 am

Lumumba wrote:Could you provide your code ?
Do you use Run Program> or Execute File> to run that *.mdb ?

Hi - I simply use "Execute File>xyz.mdb", currently this is the 2nd line in the macro with a first line which changes into the mdb's directory. Both versions (one with full path and "Execute File" and this 2nd version with a leading path change result in the same error (interestingly, after! the job has successfully! terminated). I also tried "Run Program", but this does not work (no execution).
Klaus

macroplan · Post by **macroplan** » Mon Sep 13, 2004 11:17 am

Please have a try with

Run Program>\msaccess.exe \xyz.mdb

interestingly, after! the job has successfully! terminated

Looks like a timing issue. MSched is propably faster and gives that message (but maybe not modal, and therefore its in the background or msaccess with its higher system priority hinders it to popup till it has finished)