based on the theory that the users will not universally have full rights to
the entire drive, you can't use the registry, you can't Program Files, and
you can't use anything else that is an "ordinary" Windows folder.. between
the info here, and the info on the various Paradox and/or BDE newsgroups
elsewhere, you will see many examples of that logic..
the "collective wisdom" is to make you own paths for everything, and to
default the BDE to use you own cfg files (the old Win 3.1 default)
--
Steven Green - Myrtle Beach, South Carolina USA
Diamond Software Group
http://www.diamondsg.com/main.htm
Paradox Support & Sales
Diamond Sports Gems
http://www.diamondsg.com/gemsmain.htm
Sports Memorabilia and Trading Cards
"Frank M. Cook"
acsplus.com> wrote in message
news:485a65c7@newsgroups.borland.com...>
> really? we've had no trouble on 32bit Vista leaving the cfg file in
> Program Files\Common Files\Borland\BDE. where are you putting it? we
> create an OurCompany directory under the root and put out data there to
> get it out of Program Files. should we create a BDE folder under our
> folder or should put it in the hidden Application Data folder? we are
> resisting putting our data files in Application Data because that would
> make it too difficult for our users to back up or to transfer data to new
> computers.
>
> It looks like they've done some housekeeping and eliminated old messages
> as I don't find anything helpful in the old messages. I do have Bill
> Todd's network installation instructions. what we're trying to do now is
> manually set Registry entries for ConfigFile01, DLLPath, BLAPIPath, and
> SaveConfig. We think if we get these four keys set, our application should
> be able to take it from there.
>
> if manually setting the four keys gets us working, we'll figure out how to
> get InstallAware to automate this process. so far, we seem to have
> InstallAware setting keys on XP but not Vista64.
>
> is our list of keys correct?
>
> --
> Frank M. Cook
>
www.acsplus.com
>
