>Hi,
> Hooo.....I don't mean that....I just thinking is there others ways to make UI in VFP became smarter or maybe add-ins the others platform with VFP....to make VFP not only good in DBMS, also UI.. First contact for users with our Application is UI....am i rigth....I just want to make it perfect:)

You can always go n-Tier and implement VFP COM objects for the mid-tier layer, but there's a cost associated in terms of design, implementation overhead and performance.

If you think that VB is a better platform for your UI, use VB for your UI, and put your business logic and data access in a set of VFP COM objects. This will require considerable rethinking of the application, but might make your task easier in the long run.

In my case, the advantages of VFP as a development environment outweigh the disadvantages of the non-standard UI in most cases. There are times, for example, when I'm writing an application that must be used by people who rely on Active Accessibility, or where a specific visual control must be used that isn't easily supported with VFP, that I'll split the user itnerface task out from the rest of the application; I tend to go to something like InterDev and rely on a browser to provide and manage the user interface, which can ease some deployment issues, but that's a decision based on what I know and what I am comformtable doing. If you like VB, there's nothing to prevent you from using VB, or any other language that can either access VFP dtaabases via ODBC or ADO directly, or can access things across a COM interface via a set of VFP COM objects.

If you can't do what you want with VFP, go use something else for the tasks that you can't do with VFP. If you need VFP for certain aspects of your application, you can design your application to talk to VFP through COM.

Ed