Barbara,

Once again, thank you so much for pointing me in the right direction. After many clicks through trial and error, I found a copy of my "rootclasses.vcx" library in my LABLOOK project and in the "compile-time" path. That file was being seen first during the BUILD stage. The real "rootclasses.vcx" contained in another project called MYTOOLS, which contained the correct Refresh code, was only being seen in the development environment.

I had copied that class library to my LABLOOK project intending to start using it within the LABLOOK project instead of the library in MYTOOLS. I was going to try and change the parent class for all my classes within LABLOOK to the VCX file now contained within the LABLOOK project. I remember reading about a utility someone had created that aids in changing the parent class of subclasses. Have you heard of what I'm talking about?

When I started on this project (Lablook, my first) I thought I wanted to setup a project (MyTools) containing all base classes that I would subclass all future classes from. But then I got to thinking about it and thought I might one day unknowingly "break" an old project that I had already released as an EXE. I think I want to still have a MYTOOLS project, but just to use as a basis, I guess somewhat of a framework, for future projects.

What's the right way? Do I want to just purchase a framework? Which one?

Again, thank you so much for your assistance.

Elgin

>Elgin,
>Are all of your parent classes included in the project so they are included in the EXE? What happens if you set a path (in the EXE) to the folder with the parent classes?
>
>You can follow the code with the debugger by running the EXE from the command window and putting "Set Step On" in the code. Perhaps you could set a breakpoint for the controls that should be enabled/disabled.
>
>HTH
>Barbara
>
>>I have a "parent" form with code in the Refresh method to set the Enabled property to .F. for all Controls contained within that have an "Editable" property set to true. All the forms in my App are based on this form. This is a routine I got from AppDev. My question is this: When I run my forms in the VFP environment the routine works and all controls are disabled according to the current state of the "editing" property on the form. However when I run a compiled EXE of my App the controls are enabled and are just ignoring the Parent class methods.
>>
>>Note: My "base" parent classes are located in a different project and directory than that of my app.
>>
>>I don't understand why it can work in the VFP environment but not for the compiled version.
>>
>>Thank you for your help.