>>Howdy and grand rising,
>>
>>Receiving the attached error message. The Syslog.dbf is the database i am using to capture my errors. My question is why it's looking for that file in my c: drive. I have the application on my home server identified as T: drive. Is it necessary to hard code paths?????
>
>No, but make sure they're available. The mapped drives (see other threads these days, there was another to the same effect, active today) are unreliable. They may be disconnected at any time and for various reasons, and they're supposedly reconnecting on demand, but VFP isn't on the list of apps who know how to ask for it, it was discontinued before that became customary.
>
>So use UNC. The reason it's looking at this location is that, in absence of T: drive, it looks at the folder at hand, and that's where the desktop shortcut was.

In addition to what Dragan sttes, one thing that could crop up from time to time is the current directory might not be where you expect (I do recall it occurring often after moving from DOS to Windows). It often occurs after using something that might let the user navigate folders (e.g. GETDIR(), GETFILE(), PUTFILE(), etc. or use the Common Controls ActiveX ), or upon return from an external program. Sometimes calling Windows API functions could cause the current directory to change unexpectedly. The usual workaround is to save the current directory prior to any kind of activity that might change the current directory, then restore it afteerwards.