>Hi Russell ---
>
>
>It *could* be that you do not have write access to the directories where Fox is stored on the LAN? Therefore, your changes cannot be accepted and, hence, the button behaviour?
>
>John
>
>
>>
>>Having subclassed all VFP30b classes and stored in a Cals Library on our network. From the options menu 'Form' tab:
>>
>>Selecting 'Formset' and pointing to the new library , selecting the subclassed 'scFormSet' class.
>>
>>Selecting 'Form' and pointing to the new library , selecting the subclassed 'scForm' class.
>>
>>Pressing the Button 'Set AS Default', the button gets disabled.
>>
>>When creating a Form, Foxpro still defaults to the original base form, instead of the form I subclassed. Inspecting the 'Form' tab again shows the 'Set AS Default' button as being enabled again. Why does it not accept my new library, subclasses as the default's. this happend both with VFP30b, VFP50
>>
>>Thanks
>>
>>Russ


Hi John
I suspect it might have something to do with the Lan. I'll setup another Class Library (Local) today and see if it will accept it. I notice that it will write this assignment to the Registry or at least try to. In my case the registry entries are "". Any restrictions on writing to the Registry that you know of.

i'll post any success here.

Thanks

Russ