>I have a form where I would like to have the data fields in the top half and a grid in the bottom. I am using mclistobjonformedit and can get my fields populated with the selected record on the grid if I trigger a refresh myself. I am hoping someone has already determined the other required methods and code snipits needed to have the form function for add, save, delete, cancel.
>
>There is no documentation on using the "mclistobjonformedit".
>
>My main problems are:
>
>Where is the appropriate place/or mechanism for "refreshing" my form based on actions in the grid?
>
>What other "standard" code/methods should be added to "mclistobjonformedit" to have the buttons, highlight, and other capabilites work like "mclistobjedit".
>
>Someone who has a form working like I've described should have visited all these issues. Can anyone share the required methods and code?
>
>Thanks,
>
>Gary Pike.


Hi Gary,

The cListObjOnFormEdit was originally started when I took a day of tutoring with Kevin about 18 months ago. I, too, had some desire to add/edit on the same page as the grid data (it being advantageous to see the data displayed in the grid when maintaining a record.) Kevin and I made some changes to a subclassed cListObjEdit and renamed it. I thought that it was only in a copy of the custom controls class that I was taking with me, since it was not 'production ready' but here it is. This was in 6.0b.

When I upgraded (making the jump from 6.0b to 6.1.2) I discovered while testing the form in which I had this working (limping?) that there were numerous problems in getting it to work and I had too little time, so I ripped it out and replaced it with the standard cListObjEdit and the modal form. I've not yet had the time to address this.

The problems that I saw included (this was used for child data):
1. Getting the form to enable the grid when there were no records.
2. Enabling the data controls when attempting to add data.

Kevin was gracious enough to keep this control in so I wouldn't lose it when upgrading. I'm hoping that enough requests are made that this will eventually become a fully functioning control. Maybe Version 7.0?