>>>>Sam
>>>>
>>>>Do not use data environment to open tables. It is harder to change sequence of opening. Use the LOAD method of the form.
>>>>
>>>>Use private data session forms by default.
>>>>
>>>>This is what I was talking about before. You are trying to learn but there is no value doing it the hard way.
>>>>
>>>>>Hi Sir,
>>>>>
>>>>>The Data Session worked. I have set to PRIVATE for both forms. Do I need the AGAIN in my code since I have already set my Data Session to PRIVATE? Please confirm.
>>>>>
>>>>>Thanks,
>>>>>Sam
>>>
>>>Hush! you're confusing the poor guy! Take no notice, Sam. I've never had any problem from "sequence of opening" nor was I aware that it could be a problem. If it should prove crucial in future then you can do it manually, when you have more experience.
>>>
>>>With respect, Mike.
>>>
>>
>>Appreciated Terry. :) However... there was an issue today where Michael Savage was reworking a vfp7 view to vfp9. This view could be broken into two pieces to handle the vfp9 group by. If he did break it into two views, he would have to be careful of the sequence that the views are in the DE.
>>
>>I understand the DE is easy to use, but that's only from a certain perspective. Opening them in the load is IMO the most flexible. I understand it's not drag and drop easy, but it's easier than ripping all the tables out of the DE and putting them all back in a different sequence.
>
>That sounds like a very obscure problem. Again, one that comes at an advanced stage. And, as you said, it's a conversion issue.

Doing things in code is often better. That one would have to break the query in two indicates that one has to be aware of the sequence, albeit in cases where one query depends on another. One has to be aware of the sequence of the columns in a grid. Manipulating their sequence in the designer is also difficult.