Something got goofed up and it sent it before I wrote anything...

Anyway, I'm starting to get a better idea of what's involved in this. I thought there was an application class out there already and all I had to do was make an object out of it.

The budget won't allow buying a framework, but I also don't need anything too fancy. The current version of the app uses straight procedural code to activate the menu and do a read events. I'd like to take it into an object, but I don't need it to do much more than that.

I'll look at TasTrade, and run the wizard again. Plus someone mentioned another website that has a helpful explanation. I think I can figure out enough to write my own with all this help.

Thanks,

-Michelle



>Easy question, Yes. Easy answer, no.
>
>When you begin to talk about an application object being added to your design you are entering the realm of the application framework. Any application framework that is going to work is going to need to be designed to meet all the requirements you may throw at it. The framework to a VFP application is similar to the frame of a house. With the frame of a house you expect it to suppport all of the walls and the roof and everything else you decide to put in the house.
>
>An application framework is the same. At the center of a framework is the "application" object. What that object is and what is does is fully dependent on the design of the framework. There are some designs that have the one object that has methods for launching forms, checking security, issuing the read events and clear events commands, etc. Other designs have multiple objects, an Application object basically is responsible to start the app and to create the other objects. These other objects may be a from manager, a menu manager, a data manager, etc.
>
>All of the objects are designed and coded as class definitions from which the corresponding objects can be instantiated. The code all resides in the class definitions.
>
>You can study the code in TasTrade (the sample application that ships with VFP) to get an idea of what is involved.
>
>In short, there is more to doing what you are after than simply finding and using an application object. Your best bet would be to get one of the commercial frameworks and study it and use it.
>
>The development of a framework can take many person months of work and that means no production work is getting done while the framework is fleshed out. The price of the commercial frameworks (around 400 dollars or so) is small potatoes when compared to the amount of work required to create your own, especially while you are learning what they are in the process.
>
>Hope this helpful.