dbTalk Databases Forums  

VFP 6/9: registry.prg Terminology

comp.databases.xbase.fox comp.databases.xbase.fox


Discuss VFP 6/9: registry.prg Terminology in the comp.databases.xbase.fox forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Gene Wirchenko
 
Posts: n/a

Default VFP 6/9: registry.prg Terminology - 09-21-2006 , 03:30 PM






Watch carefully as Gene gingerly pokes his way through the
minefield called the Registry.

First, I need a pointer to documentation for registry.prg. I
have tried Web searches, but have come up with nothing.

I am having trouble with the terminology. It does not seem to be
consistently used.

1) HKEY_CURRENT_USER is called a key, and one text on Windows
95 that I have calls it a category.

2) The area where I want the values to go is variously called a
key, a subkey, a key path, and a lookup key.

3) The actual item in the previous is called a key or a subkey.

4) The actual item value is called a key value.

What is the correct terminology?

registry.prg has functionality for deleting #2 but not #3. This
puzzles me. I have tried concatenating (as in #2+"\"+#3), but it does
not work (error 2). When I try to set #4 to "", I get error -103.

How do I delete one key value without having to delete the whole
works?

If you see smoke from a Kamloops direction, it may be another
forest fire, or maybe, my Registry will be hosed.

Any help will be appreciated.

Sincerely,

Gene Wirchenko

Computerese Irregular Verb Conjugation:
I have preferences.
You have biases.
He/She has prejudices.

Reply With Quote
  #2  
Old   
Gene Wirchenko
 
Posts: n/a

Default Re: VFP 6/9: registry.prg Terminology - 09-21-2006 , 04:43 PM






Gene Wirchenko <genew (AT) ocis (DOT) net> wrote:

Quote:
Watch carefully as Gene gingerly pokes his way through the
minefield called the Registry.
I have made some more progress, but I have a weird problem that
suggest that I am missing something. Here is the sequence:

OpenKey for HKEY_CURRENT_USER on "Software\Adobe\Acrobat
Distiller\PrinterJobControl", creating it. This works.

GetRegKey, SetRegKey, GetRegKey for "application". The first
picks up any previous value, the next writes, the last verifies the
write. This works.

SetRegKey again for "application" to a different value. This
works.

I GetRegKey and get the different value. This works.

I GetRegKey for a *different* key and get that same newe value.
This happens even though the different key is not in the Registry!

CloseKey()


If I then OpenKey, GetRegKey for the different key, I get "" as
expected.

Why the different values?

Sincerely,

Gene Wirchenko

Computerese Irregular Verb Conjugation:
I have preferences.
You have biases.
He/She has prejudices.


Reply With Quote
  #3  
Old   
Gene Wirchenko
 
Posts: n/a

Default Re: VFP 6/9: registry.prg Terminology - 09-22-2006 , 12:22 AM



Gene Wirchenko <genew (AT) ocis (DOT) net> wrote:

Quote:
Gene Wirchenko <genew (AT) ocis (DOT) net> wrote:

Watch carefully as Gene gingerly pokes his way through the
minefield called the Registry.
More progress, but I do not understand why so many of the
functions open and close the key. .OpenKey() has a parameter to allow
the key to be created. It is the only way to create a key. Despite
the other function closing the key at the end, it does not close the
key at the end.

What am I missing? What purpose does closing the key serve?

[snip]

Sincerely,

Gene Wirchenko

Computerese Irregular Verb Conjugation:
I have preferences.
You have biases.
He/She has prejudices.


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.