I have a Windows service that monitors a directory for a file. When the file arrives, I need to launch Access and do some things with that file through a macro.
I am successful at doing this from a command line, but something goes wrong when I incorporate this into the service.
I am using the Shell Command to launch the program, and I see that, sure enough, MSACCESS.EXE appears in my processes list, but nothing happens. I am assuming it's due to the user interface-less nature of services, but I don't know how to get around this. Any help would be appreciated.
I am successful at doing this from a command line, but something goes wrong when I incorporate this into the service.
I am using the Shell Command to launch the program, and I see that, sure enough, MSACCESS.EXE appears in my processes list, but nothing happens. I am assuming it's due to the user interface-less nature of services, but I don't know how to get around this. Any help would be appreciated.