Wow are you going to feel stupid. Here is how I do it in calling a VI job from Access.
ChDrive "M"
ChDir "M:\Mas90\HOME"
Shell("M:\MAS90\HOME\PVXWIN32.EXE ..\LAUNCHER\SOTA.INI ..\SOA\MAS90 -ARG ..\VI\VIWI0F W O DIRECT MANUAL HHA")
Notice that the drive letter M is relative to the work station. In your example of course it works on the server. That is where MAS is located on the C: drive. But from the work station where is MAS located? M drive? Z Drive? I bet it's not the C drive you are using.
Our workstation does not have a drive mapped to the mas server. When the workstations are setup we use \\servername\mas90 to indicate where mas is located.
I copied the ..\vi\VIWI0O files from the mas server and placed it on my test workstation and called PVXWIN32.EXE on the workstation.
In your example the program is still run on the workstation. I'll try mapping a drive for testing purposes and see if I can determine what the differences are.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.