>Very rarely - but consistantly - One of my LAN users receives this error.
>
>Any suggestions?
>
>I think that my temp directory is not being recognized/enforced - what is the best way to test for LAN users using Local PC temp directories during operations?

%1 is the first argument passed on the command line - typically, this indicates that either a set of double quotes is missing in a shortcut or registry entry and a path with a space or other delimiter is specified, or you've pointed to a path using a mapped drive letter where the mapping doesn't exist or is inconsistent from machine to machine. I'd check the drive mapping issue first, since that's the most common glitch, and it usually requires that someone else, responsible for a login script, get involved to fix things.

You need to check -before- VFP starts to ensure that the temporary file directory for the CONFIG.FPW exists and is writable; the real problem comes when you aren't quite sure what CONFIG.FPW specifies for a temp directory, often because the exact location of the CONFIG.FPW in use is in question. I solve this with a launcher app - it builds the CONFIG.FPW for the workstation at runtime, ensuring that the directory exists, and then launches the app using the -C to point at the specific CONFIG.FPW for that station. I wrote my launcher in VBScript, so that I can handle issues like no runtime, an invalid temp directory, or a component that requires updating before VFP gets fired up. Of course, this means I need VBScript installed on the PC - which is done as part of installing WSH during my app installation.