I just spent the last 4 weeks developing an Access '97 application using a workstation with Windows '98. One of the things this application does is to dynamically call another application to print thermal bar code labels. The application tested out fine on the '98 box.<br><br>Yesterday I migrated the application up to our Compaq 3000 server running Windows NT 4.0. Alas, when testing the application there, the call to the label printing application failed (a window pops up with the script "File not Found" (no other information, I don't even know what application is isuing this window; the "file" that is "not found" is not shown in the window either).<br><br>Carefully checking, I made certain that the file and path-names were correct. Stymied and baffled, I finally went to the DOS prompt and looked at DOS file names. Out of desperation, I modified the Visual Basic code in my application to use the DOS file name instead of the Long file name and the call worked. <br><br>Now I am wondering if there is something unique about Windows NT, a parameter or something that has to be set in order to use long file names in dynamic calls ? Can anyone shed any light on this? <br><br>The following shows the original call (that works fine on Windows '98 but fails on NT 4.) and the call using the DOS file name that works. <br><br><br>**ORIGINAL CALL THAT WORKS ON '98 BUT FAILS ON NT 4.0 :<br><br>Dim stAppName As String<br><br>stAppName = "C:\Program Files\BarTender\bartend.exe""/f=C:\PROGRAM <br> FILES\BarTender\Excel Formats\FARM LIBRARY LABEL 4X2.BTW/FP/X"<br><br>Call Shell(stAppName, 1)<br><br><br>**REVISED CALL ON NT 4.0 THAT WORKS (USING DOS FILE NAME):<br><br>Dim stAppName As String<br><br> stAppName = "C:\Program Files\BarTender\bartend.exe""/f=C:\PROGRAM <br> FILES\BarTender\Excel Formats\FARML0~1/FP/X"<br><br>Call Shell(stAppName, 1)<br><br>Where "FARML0~1" is the DOS file name ........ this seems crazy to me, but it works.......... any ideas as to why ? <br><br>Paul