Re: Re-Post: Project Path References

Thanks Bill!

I'll take advantage of the SET PATH command, and it won't be all that big of
a change, because I store all of the application paths in a control table,
so that I can logically switch the code when running in a development or
production environment. It will just be a matter of creating the path
string.

I believe that what tripped me up on this whole thing was having a different
directory structure in the production and development environments. As
someone said in my intial post above, the APP apparently doesn't resolve the
paths the same way a compiled EXE does, so I'll add the SET PATH
information.

Thanks again!


.

Loading