>

---

>
>The first point make me very angry!! Computer don't work as my coding told!! What a Computer language!!!
>If you want to try how the poor facts do:
>
>1) make a form class named fTest and give a grid on it with recordsource "TableA"
>2) at Ftest.Load, you need to put the coding on loading DE:
>
>

>* Ftest.load
>If !used("TableA")
>  Use TableA again in 0 order tag KeyA shared
>endif
>
>=CursorSetProp("buffer", 5, "TableA")
>
>If !used("TableB")
>  Use TableB again in 0 order tag KeyB shared
>endif
>
>=CursorSetProp("buffer", 5, "TableB")
>
>SELECT TABLEB    && Change the Current Work Area to TableB, this make you CRY!!
>

>
>3) make a form to call the class:
>
>Set Classlib to myCls.vcx additive
>public fTest1
>fTest1 = CreateObject("fTest")
>fTest1.Show
>
>

---

>This's all, you will find that the Grid MUST show TABLEB data even you adding coding on Grid.Init:
>
>This.Recordsource = ''
>This.ColumnCount = -1
>This.Recordsource = "TableA" && unbelievable, this line of code is ignored!
>
>It still show TableB data and Ignore your last coding on assigning Recordsource!!! Angry!? /._.\"
>Of cos, all your controlsource assignment is lost!!
>
>

---

Terence,
I'm simply lost. What's expected with the above scenario is to get TableA data and what you get is TableA data :) Why would I get TableB I can't understand. With that code in grid.init it's very normal I would lose formatting and controlsources (code in columns and their controls in turn) but still I would get TableA and I get it. I deny that absolutely TableA must be selected first but I'm aware that there might be cases where you should.
(why I feel myself as the defender of lovely grid control:)
Cetin