Kimsue,
You know, I just had another thought on this... (Some times I get so "caught up" in the newer OOP world...).
A simple solution that is quite viable, is to do this:
Create your form class. (You've done this already).
Create a new form, using your Form Class, but don't actually *put* any objects in it that you wouldn't releady put into your form class. Open the Data Environment, and put in the code you want.
Save the form, but put it some place like CLASSES\BASEFORM
Then, instead of clicking the "New Form" button when you want to creat a new form based on this form, simply copy the form, and rename it. Then, when you open the copy of the form, (which you would then place in FORMS\) you have all of your "Base" elements for the form.
Now, the really clever bit is, because this form was created from you "Form Class", any changes to the Form Class you make will still get inherited in your "Copied" form, and your DE will remain in tact. (It's just the difference between using a "Form Class" and using an actual "Form" that you copy and rename instead.) The benifit of which is, though, you don't have to re-write the code every time. (I used to use this practice all the time in my 2.6 days, by copying a "Like" form anytime I started a new one... That way, I only had to change a few things, and add the appropriate fields to the form. VFP is really no different in that regard).
So, hopefully this, while a kludge, solution would work well for your needs.
Best Regards,
Scott
Please let me know if this has helped
![[hammer] [hammer] [hammer]](/data/assets/smilies/hammer.gif)