>The other way is that when you launch a child form, the child form can load another instance of your student table (using a similar naming convention) using a VFP "USE" command and then call the CDE's AddCursor method to register the newly added cursor to the managed cursor list in the CDE (just like it had been set and specified at design time).
>
>Personally, I think that I would make the Student form the "parent" and use a multi-instance formDataManager as the base form. Then, just use the standard Codemine find/list capabilities to load the correct student. This way, you can load as many students as you like and it is much cleaner.

Thank you for your answer, Gary. I am trying to produce an interface similar to MediSoft (you can download a demo at www.MediSoft.com) which allows user to filter and do neat things from the navigation form and call the editing form if/when necessary. This way also allows reuse of editing form from different places.

I have wanted to avoid it, but maybe I would need two CDEs, one for navigation and another for the editing form. The editing form would receive the desired PK and requery the cursors which would be created empty during load.

Alex