>>The problem comes when your project is hard-coded internally as C:\MyApp and you try to run it on the network on F:\NetApp. The EXE which you placed on F:\NetApp will STILL look at C:\MyApp first.
>
>But C:\MyApp won't exist on the user's hard drive. So it won't find it there, and it will look in the current directory, which is where it is. Other than the extra work of checking a non-existing directory first, I don't see why it would be a problem. It would be nice, though, if you could hardcode the relative path off the current directory, but I didn't see any way of changing the path. Is there?

How about a little tricky game with paths stored in various places within the project file and (far trickier) the .dbc? There's a function to retrieve the relative path from one path to another (haven't used it for years, its sys(something)), so it could be stuffed into the project to replace paths with relative paths. Should do with .scx and maybe .vcx (carefully).

disclaimer - don't do this at home and backup first. I haven't tried this since FPD2.0.