>5.1 didn't support views; 6 did, but I had fooled the 5.1 to use a couple of views. Then they came up with an enterprise version which had support for remote views - only you had to have your apps using views already. The time between "can't use views" and "if you're using views we got good news for you" was about 18 months - there's no way I could have switched so many apps to use views, not under VPM.

Yeah Version 7 (according to them) supports views. uhh huh, yeah I have version 7 and 'support' is not the operative word. It's not that it's impossible to use them, it's just that it might as well be.

>They also still used a lot of public variables in VPM 6.0b - and allegedly had done away with them in later versions. The trouble is that most of these variables were the only way to tweak the framework's behavior, and references to them were scattered all over the code. Having them was bad enough; removing them would be a pending disaster.

They got rid of some of them, but there's still WAY to many.

>The error handler is probably the worst experience I had with VPM: what it does is log the error (that's OK and pretty thorough, though the output from Display Memory is clogged by at least two pages of public vars and arrays), then closes all tables, then tries to resume running your app. Having the tables closed will get you another error within a few lines... so after about 60 clicks on Continue you lose patience and kill the beast, restart VFP and try to figure where you left off.

Yeah this was a pain in the neck too. I finally came up with some workaround for that problem - turn it off....and hell even that wasn't as simple as it should of been.

>Set Rant OFF
me too.