Hello Pavel,

It is really a big question that you ask. there are many potential choices and programming decisions that can be made to accomplish your task.

When you have a child table, then it can be displayed either in a List or in a Grid. Grids are very alluring, but I've tried them and prefer lists. Many others prefer lists also. Grids have paint problems and other problems. You can use them, but many who've tried decided not to.

Regarding Lists you may want to use VFP's native List control. Or, you may wish to acquire one that is improved. I use VFP's native list control for this. However, some that you acquire as an ActiveX control may allow direct editing into the List object rather than requiring that something pop up when you edit.

I prefer that something pop up to edit in rather than edit right in the list, but different tasks have different preferences.

Next, when the something pops up to allow editing of a child record, then should this something be a Form (modal) or a container or what. In my system I used containers for this. But I tell you most people use Forms. My containers work good now, but it took a lot of work to get them that way, a lot of programming at class library level before all problems worked out. Forms are much easier.

But once you get this something popping up you can put a List on that something and theoretically allow for unlimited drilling down into more child tables.

Of course the normal thing to do would be to buffer all those tables that are changed and save them all at once. I assume you're using private data sessions on your form where you're doing this editing. Your form that pops up needs to be modal and not use private data sessions because you want it to use the data from your current data session.

I recommend you use Lists and modal forms for this task. It is a lot of fun programming ... ... good luck!!!

Wally Noll