> I'm a little confused by the notion that you make your own paths but don't
> use "ordinary" windows folders.
don't use Program Files or any other folder that Windows put there by
default.. the ability to put your own stuff under there depends on *many*
things under Vista..
it would be so much easier to say "don't use Vista".. but not everyone has
that option..
--
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:485a846a@newsgroups.borland.com...>> 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..
>
> I haven't checked the Paradox groups. that's a good idea even though we
> use dBase files.
>
>> 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)
>
> we do use cfg files. I'm a little confused by the notion that you make
> your own paths but don't use "ordinary" windows folders. we've been
> putting our data in our own path but that is what I'd call an ordinary
> folder. I don't see the issue in some users not having rights to that
> folder. if a user wants to create a rights system to limit access to our
> program, why should I defeat that by putting my data in all
> users\application data?
>
>
>
> --
> Frank M. Cook
>
www.acsplus.com
>
