Dear Cory,<br><br>> If I went with your method would it be possable to have a asp page link to the program and have it run and also to the asp page that would display the data?<br><br>I don't believe so, that's what ActiveX controls are used for in ASP.<br><br>>I was thinking that maybe after say 10 seconds of running the first link it could direct the user to the second link which would the display the info.<br><br>>Do you think that would work?<br><br>I seriously doubt it, and it's a terrible 'hack' anyway.<br><br>First, I am not familiar with the new IIS5 functions like ASPExec. Nick is probably correct about permission related details causing your problem. If so that is your first and fastest solution. Anything else will require a coding effort well beyond ASP pages.<br><br>There is 'almost always' more than one way to achieve your goal. In your case it really sounds as though the Microsoft DNA design would call for you to take the code from your console application and build an ActiveX control out of it by wrapping a COM interface around your internal code. Then an ASP page can use it to accomplish it's task and display resulting data.<br><br>Another approach to accomplishing this would be to use the FileSystemObject and associated objects to do this straight from ASP. You will still have to deal with permissions though, probably in the same way you have to now.<br><br>Keep trying... you will get it working.<br>-pete<br><br>