Getting ini value

We now need to add a security file and install it to the data folder .
The installation works fine now if the data files are on the same drive as
the program. We are running into a problem
where the data directory is on another computer. with a different drive
letter.

We store the driver letter on all computers in the
Users\Public\publicdocuments\amsoft/files. The problem is I believe this
location will change with different versions of windows.
So I did find a script get ini. How do I tell it to look at the right
directory. The file it will be looking for AmsOptions with a section of
setup and data DrivePath=c:\hcsdata.

If it is on the c drive everything works fine. Our problem is when the
data resides on a different drive. I could give them a choice of drive
letters but most of our users would not
know what to choose.

Thanks
Gary

Gary,

> We store the driver letter on all computers in the
> Users\Public\publicdocuments\amsoft/files.

I think the equivalent of "Users\Public\publicdocuments" is
%_CSIDL_COMMON_DOCUMENTS%

Friedrich

> We now need to add a security file and install it to the data folder .
> The installation works fine now if the data files are on the same drive as
> the program. We are running into a problem
> where the data directory is on another computer. with a different drive
> letter.
>
> We store the driver letter on all computers in the
> Users\Public\publicdocuments\amsoft/files. The problem is I believe this
> location will change with different versions of windows.
> So I did find a script get ini. How do I tell it to look at the right
> directory. The file it will be looking for AmsOptions with a section of
> setup and data DrivePath=c:\hcsdata.
>
> If it is on the c drive everything works fine. Our problem is when the
> data resides on a different drive. I could give them a choice of drive
> letters but most of our users would not
> know what to choose.

Hi Gary,

If you use our ProPath templates to manage where the data files go, then
you can also use our FirstDeploy feature to solve your problem.

You'd simply specify the file and that it needs to be deployed if it does
not exist.

Then when the user runs your program it will end up in the correct place no
matter what the OS version or where they have picked to have the data
reside (server or local).

In the case of server based shared data you can also choose to have ProPath
maintain a data location for user specific data (such as INI and security
files) on the local PC and have FirstDeploy use that as a target
destination.

Charles

--
-------------------------------------------------------------------------------------------------------
Charles Edmonds

cjeByteMeSpammers@lansrad.com (remove the "ByteMeSpammers" to email me)

www.learnh5fast.com - Master building web and mobile apps with Clarion H5!
www.clarionproseries.com - ProDocument, ImageEx, ProScan, ProImage, ProPath
and other Clarion developer tools!
www.seal-soft.com - The xProduct Clarion templates - xWordCOM, xToolTip,
xDataBackup Manager and more!
www.ezchangelog.com - "Free ChangeLog software to manage your projects!"
www.setupcast.com - "A revolutionary new publishing system for software
developers - enhanced for SetupBuilder users!"
www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
and Forms - Now with PNG support!
www.fotokiss.com - "World's Best Auction Photo Editor"
www.lansrad.com - "Intelligent Solutions for Universal Problems"
-------------------------------------------------------------------------------------------------------

> Friedrich
Thanks for the ideas guys one of theses will certainly work.

Gary