>Ed:
>
>Thanx for leading me in the right direction. The problem was lCreateKey was always false. The strange thing is there is a lCreateKey property that I set to true, but it doesn't get passed to the SetRegKey function. I had to add it to the parameter statement. In the comments for SetRegKey, it doesn't show it in the example. How would any one know?
>

Unfortunately, reading the code is required; it helps to know how the registry-related API calls work. The problem is that the SetRegKey method is really a wrapper that combines two distinct operations, opening or creating the registry key, and then creating or modifying a registry value. i don't think that MS did anyone a favor creating the method; I'd rather see two methods invoked explicitly so that the decision process was clearer. It's one reason that I keep using my own existing library rather than the FFC. I let my registry class behave in a stateful fashion, so that I can open a registry key and then set multiple registry values, using a property to keep track of the key handle.

>Regards,
>Charlie