At VFP class, the instructor told us that it's a good idea to make the whole application into an object. He did it using the application wizard. I tried that, but kept running into problems. I'd rather do it myself, anyway. I don't like wizards because I like to know what all the code in my app means. The best way for me to figure something out is to do it myself.
>
>So, could someone give me some pointers about how I go about making an application object and what to do with it when I got one?
>
>Do I still do a "read events"? Where do I put it if I do?
>
>Basically, I need the steps to turn a collection of forms into a runnable application.
Michelle:
One place to look for an example of putting most housekeeping functions in an application object is the Tastrade example that comes with VFP5 (I think, I know it came with VFP3). When I started out with VFP several years ago, I used the Tastrade application object as a model -- and it worked out pretty well.
It's worth a look.
regards,
Jim Edgar
Jurix Data Corporation
jmedgar@yahoo.comNo trees were destroyed in sending this message. However, a large number of electrons were diverted from their ordinary activities and terribly inconvenienced.