Hi Mark...

None of the manual stuff is necessary with VFE. VFE's wizards will work directly on views. VFE also let's you define metadata in its data dictionary for views, including view parameters. VFE also allows you to switch between local and remote views just by changing a single property. In addition, VFE has a lot of features built in for parameterized views to handle retrieving view parameter values and requerying, "relations" between views and a lot of other mature and well tested features related to client-server. This is all VFE5. VFE6 is even better, it's new data model is consistent with the ADO interface and actually binds controls to objects rather than fields which makes it extremely flexible with regard to changes in the back-end. I don't know much about ProMatrix, but from what you've described, if your using it for client-sever work you really should check out VFE.

>I've been using ProMatrix for 1.5 years, currently on version 5.0c.
>We will be using a mix of client-server & VFP tables & we don't expect
>to have any trouble doing this. Just be sure to use views when
>updating potential CS tables. Also, place any sql-selects that will
>be pulling from potential CS tables into 1 .prg. This will help you
>later when you need to change them over to SQL-Server or Oracale
>statements. The only shortcoming with ProMatrix 5.x is that you can't
>use all of their form builders when using views. The solution is
>to build those forms manually. It's really not that hard. I would
>build a form using the builder, see what properties it sets & then
>be able to do it manually.
>>Hello all,
>>
>>I'm just starting out a project in ProMatrix (1st ProMatrix app) and will need an Oracle backend. I've read that FoxExpress is better at C/S, but that was before Promatrix 5.1/6.0. Anyone have any comments/ suggestions/ experience with C/S and the brand new ProMatrix?
>>
>>Thank you in advance for your help.