Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Relationship designer not allowing me to create a relati
Message
De
27/05/1997 12:25:21
Larry Long
ProgRes (Programming Resources)
Georgie, États-Unis
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Divers
Thread ID:
00033670
Message ID:
00033711
Vues:
47
>I have a DBC into which I've loaded some 2X DBFs. Everything seems fine except for two things. I cannot seem to create a relation between any of the tables. Rushmore does not optimize more than one table in a SQL statement. I've used SYS(3054) to check the optimization level and one table is always optimized while the other is never optimized, not even partially. The SQL statements come directly from the 2X app which is being converted and much time was spent on optimizing them for Rushmore.
>
>Any ideas as to why the relation designer will not allow me to create
>a relation? Is it because they were imported and not created in the DBC? The keys I'm trying to link are named differently, but are identical in every other way. Both are tags in their respective CDX files. Any ideas as to why Rushmore will not optimize the second table in the query?
>
>Thanks,
>Steve Despres
>EZ Data Inc
>sdespres@erols.com

Not exactly sure of what is going on but I do have a couple of thoughts.

Firstly, the table relationship designer is different from the Database relationship designer. In the Database you drag and drop from INDEX to INDEX. In the table relationship designer you drag the master table FIELD to the slave table INDEX, just like the relationship statement.

Next, I would check to see that all the tables are linked properly in the SQL statement. The table links come first, then the filter conditions. For example

SELE * FROM table1,table2,table3 WHERE (tablea.id=tableb.id and tableb.id=tablec.id) AND tablea.field=filtercondition......

and make sure that the taable has an index for each filter condition, and that the filter conditions EXACTLY match the index expression. For example, if you have an index on UPPER(fieldname), then a filter condition of UPPER(TRIM(fieldname)) may not be optimizable.

Hope this helps...It would help us if you could show your SQL statements and index expressions....//:^)
L.A.Long
ProgRes
lalong1@charter.net
Précédent
Répondre
Fil
Voir

Click here to load this message in the networking platform