>I personally use slighlty different approach, I create CAs using Mark's builder, then add them in Form's Load via code and call CursorFill when I'm ready.


Ok.. My first stumbling block:

(I’m going to refer to CA’s built with the Mark McCasland VFP9 CA tool as “mmCAs” as opposed to native or hand-built ones as just CAs )

So far, just to get started with everything, I have manually added mmCAs to a forms DataEnvirionment using the VFP IDE. Long term, I may add them programmatically, but for now, this was just a quick way to get started.

Apparently, it is a No-No to work on an instance of a mmCA using the Builder tool after you add the to the form DE, because I see that it is creating Init() and AutoOpen() methods in the local instance of the mmCA classes, and that prevents the parent class Init() and AutoOpen() methods from running, which obviously contain some important code that needs to be run when initializing the mmCA.

If I do use the builder, and it adds local code to those methods, I can right-click on the methods and pick “Reset to Default” and the class will work fine, but that is bound to lead to problems, as I will be mainting as many as 12-15 mmCA’s in each of my forms, and I may have about 20-30 forms that I need to convert.

So, please confirm, is it a No-No to work on the mmCAs with the Builder within the form DE?

What about using the Builder on the individual mmCA class in it’s class library (outside of the form DE)? Is that ok?