Jacky-

> Form designer work fine with me ,but I wanna code the form myself ,I doubt if there is any difference between Desinger and coding ?

It's more a matter of personal preference.

The biggest difference is that if you code your forms, you are actually going to code form classes, and then instantiate them with CREATEOBJECT() instead of DO FORM. Form classes don't have a native Data Environment, but they are easy enough to also code programmatically. Going that route has some benefits for modularity.

Personally, I like being able to visually design forms (usually as classes). That capability counts as progress in my book.

That said, it is very useful to know how to programmatically define all kinds of classes, and if that is your goal, why not continue to use the class or form designer initially. Then, you can open the form or class in the Class Browser and view the code for it. You can cut and paste to a .prg if you like.

THis is very useful if you are having a problem..you can code a prg that duplicates the exact problem, and we can run it to help you track down whatever the situation might be.