I'm having a problem that may adversely affect many others. It seems that when VFP 6.0 is used with LAN cards that "go to sleep" after a period of inactivity, the next time a running VFP app is accessed, it can't find the menu.

This a compiled EXE of about 3.5 MB. The user clicks the menu to do
something and the system comes up with a locate box asking where is
MENUS/MAIN.MPR. This is pointing to the MENUS directory under my project's main directory, which does not exist on the client's machine, of course. Don't ask me why it's not looking to the EXE - I've noticed other strange things with VFP's pathing at times (can't wait till we can have true EXEs). When this problem occurs, the user can't do anything and has to End Task on the VFP app. Not a real good thing.

As these power saving type of NICs become more prevalent, we may all have this problem. Has anyone had this problem and worked out a solution? I could put a MENU directory on the client's server with the menu file in it, but then I'd have to always update two files. And would this really work or would it then just not be able to find the next thing it looks for? Running the app locally might be a solution, but I want to avoid the slower start ups when the local copy has to be updated from the network copy. And, the point is, if it's a bug in VFP they need to fix it (yes, I reported it).

Your input would be appreciated.

Russell Campbell