Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.databases.ms-sqlserver    |    Notorious Rube Goldberg contraption    |    19,505 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 19,351 of 19,505    |
|    Erland Sommarskog to J.O. Aho    |
|    Re: MS SQL Server: run external program    |
|    30 Jul 21 10:24:27    |
      XPost: comp.databases.ms-access       From: esquel@sommarskog.se              J.O. Aho (user@example.net) writes:       > On 29/07/2021 12.43, Ammammata wrote:       > Hi there,       > this is a MySQL forum and has nothing to do with mssql or ms-access, so       > adding c.d.ms-sqlserver and c.d.ms-access which also been follow-up to.       >       >       >> I'm trying to run MS Access runtime, with my procedure and an additional       >> parameter       >>       >> the command line is       >> MSACCESS.EXE c:\Sviluppo\QCT\QCT1000.mdb ;255       >>       >> without path, being it already included in the PATH variable              In *your* PATH variable. SQL Server runs under a service account, so       it does not have your PATH.              >> If I include the path in the command line       >>       >> EXEC xp_cmdshell '"C:\Program Files\Microsoft       Office\Office16\MSACCESS.EXE"       >> c:\Sviluppo\QCT\QCT1000.mdb ;255';       >> GO       >>       >> it goes into a loop and I have to kill MSSMS to exit              So when you run that command line directly, what happens? Specifically,       does it open a UI?              SQL Server runs as a service and does not have a desktop, so running       anything which has a UI is not going to work out.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca