>>5.) Unfortunately, This Data Warehouse has no clean primary keys. I uniquely identify records by combining fields from Source Tables with fields from Reference Tables. xCase does not like this on the Reverse Engineering, but it lets me get away with it. Will this lack of primary keys cause me any major problems when I Forward Engineer my revised tables into VFP?
>>
>OK, here's a thought I had last night for dealing with my Primary Key problem. Thing is since I use multiple fields to unique identify records for Joins and relations, the relationships in my xCase diagrams end up looking like spaghetti and the tables look like they consist of all keys. :)
>
>For those using xCase... Do you see any problem with me setting up Virtual Fields in my model that represent my combined fields for my Primary Keys? From what I gather Virtual Fields will not Forward Engineer, and this would make my ERD's more of a mirror image to my actual processing needs. The only downfall I see to this tactic is that I will have alot of additional Indexes to set up in the model, but Indexes are already seemed to be a major overhead maintenance task (and necessary evil) in a Data Warehouse.

Roxanne,
I would suggest the following: There is a supplier for Xcase here in the states (F1 Software, formally Neon Software outta Toledo, Ohio). They may be able to offer some help up on their site (The Foxgang (www.foxgang.com))

I have just started looking at Xcase, what do you think of it??

Thanx!

Tony Miller
Vancouver, Wa