Doug,

>>"Ease of maintenance" also sounds sweet to my ears but that's one that requires a bit of thought.

Listen, on the project I was describing, there were 2 different versions of the entire system for 2 different store locations, both slightly different, but for no real reason other than the guy didn't think about data-driven design. (He hard-coded sales-tax rates into the code, etc).

So even just modularizing a few parts of the system and getting to one common codebase made maintenance much *easier*. Getting down to 1 customer lookup routine, totally encapsulated, instead of 14 x 2 versions greatly simplified future maintenance and also future development. Multiply that by dozens of similar parts of system that were simplified, and that's what I meant by ease of maintenance.

>>BTW, I've printed all and read up to Chap. 21 of the VMP manual. Speaking of ears, my eyes are sore! *g*

You're just getting to the good parts. I've read most chapters at least three times, since I did a lot of proofreading during the beta. The security system chapter toward the end is lengthy, but *very* interesting.

>>Having said that I am more convinced tonight that this is going to be THE BEST $400.00 I've ever spent.

I agree. Even if you don't end up actually using much of the framework, you'll probably get your money's worth from the documentation and studying Drew's examples and code comments (Have you looked at any of the "ZReadme" methods yet?). Well worth the money, in my opinion.