Subject: | |
From: | |
Reply To: | |
Date: | Mon, 18 Oct 1999 17:41:52 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Does Image optimize data access?
What I have in mind is:
I'm reading a data set of invoices that have the customer number in them.
The primary key for the invoices is invoice number, and one invoice number
pertains to only one customer number. I need to read the invoices serially
because I'm selecting by invoice date, which is not a key item. As I'm
reading the invoices, I need to jump out to the customer data set and get
some info about the customer. Should I code something like this:
DBGET Mode 2 Invoice
If Invoice.Cust# <> Customer.Cust# then
DBFIND Mode 1 Customer
DBGET Mode 5 Customer
End-If
The purpose of this code is to eliminate an unnecessary DBFIND/DBGET to the
customer data set if that customer's record is already in memory. What I
want to know is should I code this, or does Image do something like this
already? IOW, if I do the DBFIND/DBGET every single time, am I wasting
resources by forcing Image to re-read a record that may be in memory
already, or is Image smart enough to not do the record retrieval if the
record is already in memory?
Thanks, as always, for any assistance.
Jim Phillips Manager of Information Systems
E-Mail: [log in to unmask] Therm-O-Link, Inc.
Phone: (330) 527-2124 P. O. Box 285
Fax: (330) 527-2123 Garrettsville, Ohio 44231
|
|
|