RE: Performance of ODBC vs. other access methods

Nope...for example in the software there is a "Company ID" field.  The
software doesn't support multiple companies so the value is ALWAYS 1.  I
figure this was something that was planned but never implemented (or
it's the way it's implemented here... 


Thanks,
Tommy Holden


-----Original Message-----
From: midrange-l-bounces+tommy.holden=hcahealthcare.com@xxxxxxxxxxxx
[mailto:midrange-l-bounces+tommy.holden=hcahealthcare.com@xxxxxxxxxxxx]
On Behalf Of rob@xxxxxxxxx
Sent: Wednesday, September 06, 2006 9:21 AM
To: Midrange Systems Technical Discussion
Subject: RE: Performance of ODBC vs. other access methods

Don't forget, key order is also important in WHERE clauses.  For
example, 
you may have a file with 90+% of the records have an "active record code

field" with a value of "A" and a few records with a value of "D".  A 
simple example is an item master.  While the item number should be a 
unique key, you may also want a key with active record code and then the

item number.  This way you can sort by the item number for all active 
records.  Maybe this is what you are seeing?

Rob Berendt