... primary keys. I would have a CUSTNO (or similar) in both files. And not allow users to change them. I am planning to do some speed tests with a DBSetRelation() & setScope() and with just OrdSetRelation() to see if there are any significant speed differences. James
... does add a scope, but SET RELATION does not. I thought that SET RELATION just called ORDSETRELATION() but I guess I was confusing it with DBSETRELATION(). I learned something new. Oddly, however, it is still using a scope so it should have the same speed as just setting a scope I would ...
... record number for the "go to" is based on the expression specified by <bKey> and/or <cKey>. ORDSETRELATION() is identical to DBSETRELATION() (and the SET RELATION command),. but it also sets up a scope on the order in the child work area. This means that whenever you select ...
... things are added to the test. ( I Still have to test using MULTIPLE index ) I added two RELATION-options // Set a relation from BILL into CUST DBSETRELATION("CUST", {|| ("BILL")->CUST_NO}, '("BILL")->CUST_NO') and // Set a selective relation from BILL into ...
... things are added to the test. ( I Still have to test using MULTIPLE index ) I added two RELATION-options // Set a relation from BILL into CUST DBSETRELATION("CUST", {|| ("BILL")->CUST_NO}, '("BILL")->CUST_NO') and // Set a selective relation from BILL into ...
Hi all, I have a xBrowse which has a relation between two databases... dbSETRELATION( Familia , {|| (Articulo)->CodFam}, "(Articulo)->CodFam" ) So I haveit indexed by 1.- CodFam 2.- Name I create the xBrowse like this: ...
Hi all, I have a xBrowse which has a relation between two databases... dbSETRELATION( Familia , {|| (Articulo)->CodFam}, "(Articulo)->CodFam" ) So I haveit indexed by 1.- CodFam 2.- Name I create the xBrowse like this: ...