Hi Tevye,

I believe of minimum work and max power. My Philosophy was the concept of OPD - Other's people data dictionary<s>. If you need a relation just add it into your MS SQL or into the DBCX or the VPM DD. VisualRep will grab those relations including fields format, fields caption, input mask and more. If you need to create a relation via the query wizard, then that query can be copied again and all relations including fields properties are copied as well.

Maybe a dedicated data dictionary could add some power if needed in some situations. I probably may add it later on. If you have some application that does not have any known data dictionary just create DBCX DD and VisualRep will grab all info from there as well.

Regards,

Doron

The Farber Consulting Group, Inc.
http://www.dfarber.com/VRep.htm


>I have used vRep for some time now. I actually worked with Doron to craft >many of the features in vRep. I have also used FoxFire for many years.
>
>I stopped using FoxFire because I found it difficult to integrate with my >applications. I also found it lacking features that would help me create >reports with a large number of (>50) fields. I can select as many fields >as I want for the report and vRep will position them on multiple report >lines. It is easier with vRep to integrate it into my apps.
>
>I also miss some of the FoxFire features. For example, although vRep will >pick up relations from a SQL or VPM data dictionary, if the relations are >not set up in the DD creating one in vRep is quite easy but requires the >user know about relations. Having a DD that is internal to vRep (similar >to the one in FoxFire) is on my wish list.
>
>vRep does work differently than FoxFire but overall I prefer it.