>>The one with VFP7 is quite acceptable when it comes to flexibility. The good thing with it is that the codes are avaiable for you to do tweaks/modifications.
>
>Hi Jess,
>
>All frameworks (as far as I understand) include source code.
>
>The one that comes with VFP lacks acceptable documentation.
>
>Alex

Alex;

Let me add this to comments about the use of the VFP “Framework”. This of course refers to the framework included with Visual FoxPro, so there is no misunderstanding.

1. Not well designed.
2. Difficult to modify.
3. No user support.
4. Modifications, updates and bug fixes from vendor not available until next software release (VFP 8.0)
5. No Internet forum activity worthy of note.
6. Limited user interface.

Otherwise all I can say is “You get what you pay for”! :)

In reality the included VFP "framework"does make a good address book application. I would not suggest anyone take it any further unless you want to spend a lot of time analyzing the code and its structure. Then you can go ahead and modify it to work as you wish.

You may as well create your own framework if you are going to spend this much time and effort. I do not recommend anyone create his/her own framework, unless that is your product. There are so many good ones on the market without the problems cited above and in Alex’s response. Let a framework vendor supply your framework and you write the clients application. That is the perfect combination if you want to make a profit and meet deadlines.

If you want to work in a vacuum, waste time and be aggravated with a tool, just use the VFP "framework" for any serious application. A great deal of the money I have earned over the last 6 1/2 years as a Visual FoxPro developer was made resolving the issues created after someone used one of the VFP "frameworks" to create a mission critical application. My resolution to this problem is very simple. First I use my own framework, by hacking the original project. This removes the “framework” and now I have a useable application. Modifications and additions are easier. The end result is a happy client and a useable application. This has never failed to gain me additional work from clients.

One such incident had 5 VFP developers working on a project with the VFP “framework”. They hit the wall and called me in. It took me 40 hours to resolve all the issues. The end result was I received additional work from this client for the same application. I received 2 ½ times more money than the original team was paid for the original application for the additions I added. It pays to have a happy customer! :)


Tom