>the trick is the learn the framework, rather than fight it. You mean real work, not just set a property and go to lunch! >In this case, >the easy way would be to create a 1:M form, and then position it off the >main foxpro window, and have at it programmatically. Everything you want >to do is available in the framework, e.g., the child_new method which is >particular to form_toolbar_onetomany. Hank, Ok... What about the form overhead, open/close spare files hanging around. Does it seem noticeably slower when you have used this method? What about the PRIVATE datasession that VPM uses for forms, wouldn't that make reaching from form to form more difficult/slower? All this said or questioned, thanks for the response and I intend to try it out. I have pretty much convinced myself VPM is a good product and I'll migrate over to it. Why reinvent every wheel. > >There are other ways as well -- I've got a button class which hooks to the >many of a 1:M and uses the VPM mover form to add/delete/rearrange records >The main thing to remember is that the code for handling all the things >you don't want to handle is in the form, for the most part.. The class >browser is your friend. <s> Also, get to know the postadd, presave, and >postsave methods. Is the debugger your friend also? Side issue, Do you know of a good SCHEDULER OCX that would allow overbooking. You know doctors would never just see one patient when the could be seeing three! Thanks Bob Gould Contemporary Software Systems, Inc. 1665 Briargate Blvd Ste 101 Colorado Springs, Co 80920 719 574 0300