I have actually been in the same situation before. It depends on the deadline. How much time is available before the app must be tested and deployed. If at all possible, your approach is the best IMO. If not and the app just has to get out before you can lay the groundwork, then just get it done whatever it takes in as clean and organized a fashion as possible. The easier you can make it for yourself (and whoever else may come along later) to accomplish future upgrades, maintenance, reuse code and classes, etc the better. The goal of having classes and a good foundation is a good one, but you may not have the luxury if they need it NOW. It has been my experience that typically that is actually the case! :o(

As to how I am feeling, thanks so much for asking. My ribs are not nearly as sore as they were. No more trips up and down steep wooden stairs in the middle of the night for me!




>>Hi Naomi. Hope your new year is starting out great! :o) I have used a couple of frameworks liked both of them. All in all though, I prefer to work in 'vanilla VFP.'
>
>Hi Tracy,
>
>Thanks for your response. Just wondering, what would you do if you would be on my place? I suggested to have some sort of a meeting between developers and if we can agree on something and share some common code across multiple projects. I started to put some classes and progs into Common directory... But on the other hand this acctivity distracts me a bit from actually designing the application. I have it in my mind, but didn't pass the database stage yet :(
>
>Thanks again and have a good year too. I hope you're feeling OK.