>Hi Jess,
>
>>I haven't tested it yet, but in theory, to me, Load event is a bit faster than DE because the latter deals with objects. I remember an article saying that the more object contained in a form, the more slower to load. Still, bottomline is the DE's ease of use, visual environment, and high level of maintainability, which are enough reasons of preferring to use it other than the Load Event.
>
>Yes, this is a logical approach and I agree with it. My question originally stemmed from the fact that when developing forms, there is no DE available when visually designing a form class as opposed to a plain form. I was wondfering why the difference in the two situations. I guess when working with form classes, the load event is the main option. I think you could create a DE programmatically for a form class, like Codebook does, but is the obverhard really worth it for a form class. I find Codebok form classess relatively slow myself.
>
>Thanks for your response,
>Phil

You have a good point, but there is a big debate on which is better, a plain form (DO FORM) or an object out of a form class (CREATEOBJECT)? I just want to mention an article by Les Pinter saying: "I love VFP object orientation. But creating a class with no data environment in order to instantiate a single form doesn't make sense to me. All it does is make a new programmer follow a rabbit trail in order to figure out what would have been obvious with a DO FORM command. This ain't dogma, it's programming. Don't feel compelled to follow some else's rules; common sense is adequate. Write code that you and others can understand and that does what you need at a reasonable cost. There's more than one way to skin a cat. [Of course, it depends on whether you're after the cat or the skin.]"