Okay, I was trying to weasel out, you caught me.
I don't think that will simplify things for you. That just stretches the problem to not only include your current issues within VB but then you will be running into debugging your autoit scripts on top of it. I mean it should work but it will make your application less portable. If you included the dll registration directly into the exe then all you would have to do is pass the scripts to be run by the sceduler... the scheduler itself... and the dll files required for VB. If you wanted to enclode that all into a single executable it would be possible if you used my EXE wrapper shared on the Scripts and Scraps forum.
Overall it comes down to that it is your application... you are the developer so you have to make these decisions. There are too many factors that I am unaware of that I don't know that I can even make a decent suggestion for this question.
This post probably isn't going to get you any closer to your goal... just make a decision.
*** Matt @ MPCS
However, when I run put that module in and attempt to run, I am getting an error: 'Sub or Function Not Defined' in this line:
CallWindowProc lngProcAddress, lngHwnd, ByVal 0&, ByVal 0&, ByVal 0&
I called the func with:
RegisterServer frmMain.hWnd, App.Path & "\AutoItX3.dll", True