>we used to open tables via hard coding but when we discovered the power of using Data Environment, we already junk the old habit depending on the situation.
>
>It is recommended that forms property data session should be set to 1 ( private data session ) to avoid having troubles in multi-window openings.
>
You are right on this one!

>It is also the best way to visualize the relatioinship between tables, thus avoiding cyclic relations and you don't have to worry on whats going on with the other modules being done by other programmers.
>
>Please comment and send a copy to jessbanaga@usa.net !!!!!!

Janet;

If I remember correctly, the main reason why I adopted forms as classes (:VCX) was because there was a memory leak in VFP3.0 on data environments.
Secondly, I like my applications to be independant of the data directory. I mean the same application should run with databases situated in different directories.

That is how it started ... By acting like that I built myself, and you'd be surprised how very easy that is, a few base classes that open my tables.

As most of us I think, I developed a distaste for the form designer. You loose a lot of time because its implementation leaves a lot to be desired. So I naturatlly started to build a layer between the form and the rest of the system, I thought that was so that I would not have to use the form designer more than barely needed. But I ended up with an architectural layer that makes a lot of sense.

Janet, you have to think about this as follows: the more you develop your applications visually, the more escapes to the OO part of your application. How important that is depends, but most of this discussion is a matter of taste and of the kind of applications you are developing.

Kind regards,

Marc