>This might be something you have covered, since it is the most obvious solution and I'm sure its not unfamliar to you - but here goes: If you are running any PRGs then you need to replace any drive references in the compiled code that point back to the original program (for debugging purposes). We use a program that runs through the .fxp files, dumps the compiled code into a binary memo field, and then replaces d:\ with c:\, e:\ with c:\ etc up to z:\ using STRTRAN. Likewise, we have a program that strips out the path information from any forms (.scx) we might still have, and finally, if you added objects onto a visual class that have come from somewhere other than your working drive and directory and cannot be referenced back to their parent class without including a drive letter, we re-map those as well by relocating the parent into a directory that can be referenced just with ..\..\ etc.
>
>Chris

Thanks Chris. I'll work up something similar for my own peace of mind. What baffles me though (well, two things) is that everything except the data and dll's is included in the exe, and since VFP always looks inside the exe first, I don't understand why the problem exists at all. Secondly, I don't understand why it's a problem on one pc at the client's office, but not another supposedly identically configured pc. I'm still waiting to see if they can tell me if there is a difference in the 2 pc's. So far, their IT department says not. The hardware, I know is the same, and afaik, they do the setup's through their network, so the configurations really ought to be the same. One manifests the problem, the other does not.