🚀 go-pugleaf

Gerald Fay wrote:
> 

> >
> This is exactly my problem and I'm not getting answers either.
> Do you have to have navigation on the master as well?
> I can do an SQL query to link a master, detail and get all the results in
> one grid. For masterrowset the child rowset is limited to the first
> master record. Does one have to use two grids to navigate?
> 
> Also, two months ago you were having trouble relating
> grandparent,parent,child tables because a linking field was numeric. Was
> that solved in the inline? I tried to follow the thread, but it appeared
> to just drop.
> 
I'm still working in 7.0 because I developed a major part of my app
around edits that are based on rowset field canchange events, which have
a bug in 7.1.  My intention is to go back and explore changing them to
grid column valid events, but I don't want to tackle that right now. Can
someone tell us if 7.1 fixed the linking issues on numeric fields into
grandchild tables????  I worked around it by using findkey and do while
loops on third and subsequent tables, writing data to array and
displaying in a listbox.  Not editable of course; wouldn't be any use if
your trying to use the linked tables in a grid, and besides it's a nasty
looking piece of code.  I was planning to go back and clean that up too
once the inline came out.

M-1 issues notwithstanding, here's what I need to know.  How can we get
editable rowsets for use in a report (or a grid) that allows filtering
of data on both the parent and the child tables (7.0 or 7.1)?  There
_must_ be a way to do this with OODML.  I have reports that need to
update the tables as they run, and I've dealt with it preliminarily by
using a .sql query and then a separate function to go back through the
tables and mark the records closed.  In addition to having to process
the records twice, it just makes me feel insecure.  Borland, TeamB,
Gurus???

Thanks,
Patricia