Cy
Sun Sep 16 07:56:22 PDT 2007
Use of the registry was supposed to do away with having a config file for
every program and component in the system. Of course then it had it's own
problems, and in addition it has it's pluses. One that is nice is the HKCU
branch of the registry as it lets you store stuff that is basically the same
information but unique for each user of the computer. This simplifies
things such as storing window locations per user of the computer, without
having to use the foxuser which only works for a single user on a machine
(meaning it doesn't work for Terminal Services or Citrix) while the HKCU
works just fine in a citrix or TS situation.
Now we are supposed to use XML config files, which work fine for application
level stuff, but still don't work so well for user level stuff unless you
store an XML file for each user. I guess it matters not since those of us
who still have to market products have to move to something other than VFP
anyways (yes our users actually are including things such as "VFP is not
acceptable as a development environment" in the RFP's and in technical
standards. Others are specifying that their development standard
environment is .net. It's too bad, so far the .net world is a lot harder
for me, there are so many things that are complex to do in .net that are so
easy in VFP, but then the opposite is true as well.
Now to be back on topic, I never expect VFP to behave normally if I start it
by clicking on a PRG (or an FXP for that matter), since it keeps it from
running all the setup stuff, and worse yet it doesn't even run the
config.fpw that I have setup for whatever development project I'm working
with. I always start with a shortcut and then open the file, anything else
doesn't work.
--
Cy Welch
Senior Programmer/Analyst
MetSYS Inc.
http://www.metsysinc.com
"Fred Taylor" <ftaylor@mvps.org!REMOVE> wrote in message
news:uCwuyw#9HHA.5316@TK2MSFTNGP04.phx.gbl...
> Thanks. I avoid the registry at all costs if I can. I think Microsoft's
> biggest mistake was allowing everybody and their brother to use the
> registry for storage. Even for a development environment I find highly
> suspect as actually *needing* to use the registry, it should be for the OS
> and nothing else.
>
> --
> Fred
> Microsoft Visual FoxPro MVP
>
>
> "Lew" <lew@fastmail.fm> wrote in message
> news:uLEHbs89HHA.1212@TK2MSFTNGP05.phx.gbl...
>>> Hmm, on my dev box at home, neither one point to anything in
>>> HKEY_CLASSES_ROOT other than just indicating that an .FXP is a
>>> Visual.FoxPro.Compiled.Program and a .PRG is a Visual.FoxPro.Program.
>>> The .PRG also has a sub tag for ShellNew that's empty.
>>
>> Right, look further down and you'll find entries for both
>> Visual.FoxPro.Compiled.Program and Visual.FoxPro.Program, open those keys
>> and that's where'll you'll find the actual SHELLOPEN commands.
>>
>
>