>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>Personnaly, I never use the DataEnvironment (except for using the Query Builder which I use to create queries and I copy the string to my code). All you do with the DataEnvironment can be done by code and this is what I prefer.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
>I agree, in almost all circumstances. But, I have found the DataEnvironment very useful for dealing with Shaped datasets. To be honest, I haven't done much of this, in lage part because of the somewhat bizarre syntax... but the DE lets you drop and drag and attach in a way that simplifies it considerably. So, after sticking with coded solutions for qite a while, I recently took a bit of a step "back" and used the DE for such a circumstance....
>
>All of which is off-topic, isn't it?!? But, to address Jess's initial question, I like to use BAS module subs that create the connection, set the dataset, etc., in line with what Eric said -- those BAS modules can be used by any form.

Thanks Guys! All of your inputs are valuable to me because I don't want to repeat what I have done 5 years ago. I am still learning VFP at that time but because of lack of guidelines, I was forced to redo everything because my first approach was then obsolete resulting to poor performance of the application.

It's really fun earning VB which to me, it's going beyond my comfort zone: waking-up - VFP, going to sleep - VFP. I tried learning Delphi, which to me, really more impressive than VB but I decided to go with the latter because of Inprise/Borland's shakeable status as a company considering that the product (Delphi) is a full object oriented and data-centric tool. It's not secure to have just one gun in hand for you stay competitive in the software development arena.

Good Luck!