Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2002-01-01 : 23:05:21
|
| Jim writes "I have an executable program which is a large administration program. I have altered the program to allow running the import procedure with no user input. (I created a sub main and used it as the startup invoking the automated process by passing a command line parameter) The program works fine as a standalone at the command prompt or in the VB enviroment, but when I call it from query analyzer using the xp_cmdshell procedure it terminates after returning from the first stored procedure it calls through the VB program which updates the database. I am attempting to keep the user import routine and the automated import routine the exact same process so I really would like to not have to rewrite anything (it is a tried and tested large process) I am going to try a couple more ideas I have, but thought maybe I was missing something easy. Thanks in advance for your help!!" |
|
|
skaggsSQL
Starting Member
5 Posts |
Posted - 2002-01-03 : 11:02:21
|
| I am the one who originally posted this topic and thought I should update the status. I have resolved the issue and it had nothing to do with the Update on the database. I had a LOAD FORM command directly after the Update procedure which was causing the problem. I knew you could not have any user input when using xp_cmdshell but I didn't know it would be a problem to load the form and never show it. I removed this and all references to the form and everything works fine.Jim SkaggsProgrammer |
 |
|
|
|
|
|
xp_cmdshell running .exe programs