You can also build your own framework. You and your teams experience count for a lot. VFP is flexible. OOP can evolve. Classes can evolve.

Sometimes, just writing a module out through simple base class methods firing procedures is a good start. We must produce:-). And, later develop a server for your procedures and a collection class for your other stuff. There are so many ways you can do it.

As boss, you will also have to consider turnover. Staying close to the VFP engine may be a benefit. A simple inhouse "framework" or "coding standards" may provide a wider, perhaps more talented, group of prospective team members. Better to be a programmer than a user!

Your team is going to have a lot of fun! Keep a journal:-)~

>Hi,
>Thank you for suggestions.
>I used to think of commerical framework before, but I never see any download for trial, so I have no ideas on how the framework work and is it suitable for my application.
>
>Most importantly, I have to be responsible if I suggest any product to my boss.. :(
>
>I think my road is not easy, but at least I can learn something and hope I will have my own framework one day.. haha..
>
>nice day :-)
>Thank you for ideas