>I have tried building a form using the tables in the data environment; the problem I had was in setting a filter to limit the amount of data accessed by the user. There was also a problem in that as a user skipped through the parent table, there was no way to control the child record order, i.e. alphabetizing the data became impossible. I thought this was what views and SQL were meant to do. As a postscript, I have fixed the problem of private data sessions being too private, but now in updating the records on the form I get a message saying "SQL Statement too long." Any ideas? I can see I'm going to have to do some more thinking...

If you want the child table to be in a specific order, just add the appropriate tag to the relational one.

If your relational key is PARENTID, just add the order to be part of it as in PARENTID+NAME. This is what we have done when wanting a child grid to be in a certain order. It does the job well.