>>Anybody run across this? Better yet, anybody found a solution?
>
>I keep all XFRX files (zlib included) in xfrx own folder as it was shipped and then use
>
>

>cXFRX_Folder='C:\wherever_XFRX_is' 
>set default to (cXFRX_Folder )
>

I somehow don't like this - if anything goes wrong, you're stuck in the wrong directory and your error handler isn't really in charge of restoring the working directory. Maybe if you used a setting object from Tom Rettig's envlib, which would restore the previous location during its .destroy()...

But then I've seen several COM objects change folder surreptitiously - like when printing (to a file?) from a browser object or some such, with unpredictable results. The app would find itself somewhere below %system% directory.

One way out of this is to make the app's set("path") out of fullpath()ed paths - so instead of

set path to mytables additive

it's

set path to fullpath("mytables") additive

which then isn't relative to your current directory, so if you (accidentally) move to another, your app still finds the files. Still not bulletproof - you may be using relative paths in your app - but may save your butt at times.