>>Have an .exe (AIS.EXE) on a network and have attempted to create a config.fpw on each local drive for SORTWORK, TMPFILES,etc. The command line in the shortcut is: Y:\AIS.EXE -CC:\AIS\CONFIG.FPW. It is not being seen. I've expermented with VFP.exe and a config.fpw that contains only a COMMAND=quit. It works with VFP.exe, but dosn't with any other executable. I know this have worked in past releases, but have not tried it 3.0 or 5.0. Anyone have any suggestions?
>
>I am using similar functionality now with VFP 3.0b. No problems. I use the Config.Fpw to set the main VFP menu off and turn a clock on. Just out of curiousity, why don't you place the EXE's on local PCs? I have found a much better response time in doing so. Although, if you have many users, you would have to make sure they are all updated per each release. I have in the past checked version number date/time stamp of exe's on local PCs to insure that they were using the correct version. If they were not, then the users were asked to download the correct version... htwh... Steve

That is an interesting idea...guess I would then just point the default to the dbf subdirectory on the network?

Thanks for the suggestion....