>I am using the vanila text buttons from the wizstyle class for most of my form navigation - which works great, except for on one form.
>
>All my forms suck data from 2 tables, and txtbtns was smart enough to figure out which was the one I wanted to navagate across. However, on one form with a third table (and this may not be relevent) It moves the record pointer across that.
>
>I scaned through the code, and noted that it was SELECT()ing which table to use. So I deleted, and re placed the troblesome table in the Data Enviroment hopoing its position (and likelhood of being SELEECT()ed) would change, to no avial.
>
>So - how do I explicitly tell txtbtns which table to nagavate, and hot do I implicitly tell it the same when creating forms?

You'll have to modify txtbtns substantially in order to make it handle a third table. In my case, the third table was a lookup table which was also joined in a parameterized view in the grid. I added "otherparent" and "otherparentkey" properties to my version of txtbtns, which I set when I place an instance of it on the form. One thing you might do is to find the code that finds the parent and child aliases in the data environment and remove it. Set those custom properties in design mode each time you place an instance of your version of txtbtns on a form.

By the way, parameterized views used for the grid is another thing txtbtns won't handle until you modify it.