If the VBScript program uses only ado and/or fso
then change it to an include file and run the
code directly in the asp page.
If you use the command shell object, or want to
run other external programs you may well find you have
problems with permissions.
You may also find that is the external program is rather heavy there is no code to send a 'Process Done' back to
your asp page, meaning any further statements in your asp
page may run before your external program has finnished.
Another options is to create an activeX/comm control to
be used server side.