>Chris:
>
>A good way to solve this is to set the Path in the config file. The following is an example from my config. My default directory is set to the directory above \Data etc. where my project resides. Calling forms etc. using explicit pathing will get you into trouble should you ever move your application.
>
>PATH=E:\PROGRAM FILES\MICROSOFT VISUAL STUDIO\VFP98;.\Data;.\Forms;.\Programs;.\Other;.\Source;.\Import
>
>-Malcolm
>
>PS. My dad was born and raised in Lethbridge so I've heard a lot about it.

Thanks for your help. Can you put that in the main.prg instead? The reason I ask is that we have to put all of our .exe in one directory (n:) and I don't want to change the config.fpw there - it might cause the other .exe's not to work. I tried both of these in my main.prg but got an error when I tried "SET PROCEDURE TO proced.prg"

SET path to j:\mis\projects\acc_pay;.\Progs;.\Forms
path = j:\mis\projects\acc_pay;.\Progs;.\Forms

I am sure you have heard about the wind in this town then? Here's a sorta funny story related to VFP and the area where I live in. My boss is a huge FPW 2.6 fan. He doesn't know VFP at all! Most of our .exe's are in 2.6 - I pretty much have to beg to be allowed to use VFP for a project. Anyways...There is a town close to Lethbridge called Coaldale. That is where my boss is from. I was driving from Lethbridge to Coaldale one day. You know those signs that tell you how far you are from the next town? Anyways, this one said "Coaldale 2.6 KM" I just started laughing (my girlfriend was wondering what I was laughing at) when I saw that - maybe thats why he likes fpw 2.6 so much! Ah. Sorry that wasn't funny at all.