Friedrich,

> > It might be easier, and safer<g>, to simply look for the ". Such as
> > testing for /ConfigDir=" in the command line using script instead of
> > changing your runtime which is working.
>
> If that works for you, then yes do it <bg>

It does, and I will!<g>

> But I still think that you have a valid point here.

You have other things to clutter your mind with and, honestly, I doubt
any Clarion developer goes to the trouble of running a 3rd party
install with command line arguments... it's complicated!<g>

I still believe ConfigDir should be a Clarion install option handled
during the install process and written to the registry. That would
make things SO MUCH EASIER and is easily doable. Or, since the install
no longer defaults to "Program Files", just write the dang thing into
the \bin\settings folder and be done with it. If the developer
installs into "Program Files" they'll need admin rights to run the
program so they'll already have write permissions to that folder, or
have I not had enough coffee yet?!<g>

--
Lee White

RPM Report Viewer.: http://www.cwaddons.com/products/rpm/
Report Faxing.....: http://www.cwaddons.com/products/afe/
---Enroll Today---: http://CWaddons.com

Creative Reporting: http://www.CreativeReporting.com

Product Release & Update Notices
http://twitter.com/DeveloperPLUS