>I wonder somtimes about the VPM developers. I'm sure there are some good ones - but it seems like most of the ones I've met were not really too keen with their Visual Foxpro skills and depended heavly on VPM's wizards to do things...and a lot of the VPM gizmos seem (or did last time I looked at it) to be rather ridicilious to - like they couldn't figure out the proper way to get comboboxes to work so you got a textbox and a button with some other stupid control under it??? And then it didn't use the VFP DBC they tried to use their own instead - etc etc etc. I dunno - its like a RAD tool - not a true framework and it looked to me if you wanted to do anything really complicated or needed to 'step outside the box' or were a highly skilled VFP developer then VPM wasn't the ideal choice.
>So what it sounds like to me is you ended up with an app that was written by someone that really didn't know VFP very well and then used VPM's RAD wizards to write most of it and thus you ended up with a pile of junk that you now have to try to debug...bummer!

I'm sure the situation wasn't helped by the fact that the folks creating VPM didn't seem to want to be part of the broader VFP community, but kept themselves in their own corner.

Tamar