>Doug,
>
>>>I've decided to take a peek at MaxFrame. It sounds like it's built like I'd want to do. A good basic foundation but not a lot else in the sense of what it tries to do for you.
>
>One nice thing about Maxframe is the built-in code in framework base form classes to deal with "standalone" instantiation of forms that depend on app-level objects. Makes it easy to work interactively while tweaking and running forms without building the entire app.
>
>The security system (in the retail product) also is well-done, with group and individual-user exception handling all the way down to each control in your app, and also for "processes", which can be broader or smaller in scope than just a form or prg. Very slick. The freeware version has a very limited substitute, I think.
>
>There are plenty of empty methods placed strategically in the chronological event sequence that can be hooked into, and the app-level objects like oUser, oSecurity, oForms, oApp can easily be subclassed or completely substituted with your own version. Built-in support for SDT and INTL, and generous code comments whenever a VFP bug is being side-stepped to explain what's going on and why.
>
>Drew's design allows for tremendous flexibility to fit with your existing style of operation. Have fun.

David,

Just got it.

Mind if I ask a coule quick questions?

1. I figure there will be upgrades to the product. Is there a single location I can use to 'hook' my VCX's and other stuff in at? My presumption is is that there is.

2. Does the current version handle COMRETURNRROR() stuff?

3. Can one make an object on a specific form invisible?

4. How's his remote data stuff?

Thanks!

best,

DD