|
-
Jul 14th, 2000, 06:32 PM
#1
Thread Starter
New Member
I have created and compiled a VB 6 executable file. Now, I just want to run it at a specified time from within a SQL Server 7 Job.
The executable file can be run from a command prompt, but if I create a job in SQL Server and set the job step to a type of CmdExec, the step acts as if it can't find the executable. I even typed the full path name in the step.
Has anyone else encountered this problem?
-
Jul 15th, 2000, 11:32 AM
#2
Guru
I don't have an answer, but a possible workaround:
Can you use the Windows Task Scheduler/AT Service to launch your EXE?
-
Aug 6th, 2002, 02:15 PM
#3
Junior Member
-
Aug 7th, 2002, 06:55 AM
#4
Fanatic Member
What does your job step look like? You could try running xp_cmdshell ('c:\AppPath\app.exe'). This will/should work as long as you app doesn't have any forms that are displayed to the screen.
Chris
Master Of My Domain
Got A Question? Look Here First
-
Aug 7th, 2002, 07:02 AM
#5
Junior Member
xp_cmdshell would run syncronously and hang the stored procedure or job,,,,even If I don't have a UI displayed....
I ended up using the AT scheduler..hopefuly it's gonna work while I'm logged of!!
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|