Results 1 to 5 of 5

Thread: SQL Server Jobs

  1. #1

    Thread Starter
    New Member
    Join Date
    Jun 2000
    Posts
    4
    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?

  2. #2
    Guru Clunietp's Avatar
    Join Date
    Oct 1999
    Location
    USA
    Posts
    1,844
    I don't have an answer, but a possible workaround:

    Can you use the Windows Task Scheduler/AT Service to launch your EXE?

  3. #3
    Junior Member
    Join Date
    Mar 2002
    Posts
    24
    did u find an answer?

  4. #4
    Fanatic Member vb_dba's Avatar
    Join Date
    Jun 2001
    Location
    Somewhere aloft between the real world and insanity
    Posts
    1,016
    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

  5. #5
    Junior Member
    Join Date
    Mar 2002
    Posts
    24
    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
  •  



Click Here to Expand Forum to Full Width