Re: 4 - subfiles

[boothm@xxxxxxxxxxxxxxxxx]

You are right.  I would never hold out the load-all subfile as the answer, 
but my original point was that we shouldn't lock ourselves into the 
page-at-a-time subfile solution either because any system has many files 
that are 2,500 records or less and benefit nicely from 100% loading. 

I would also agree that at somewhere around 2500 records the file becomes 
unwieldy  -  just a twitch of the scroll bar rolls several pages and it 
becomes impossible to navigate to the desired record easily. But the 
response time issues are much different today than even 3 years ago.  It 
is my opinion the whole arena needs to be revisited because the underlying 
facts have changed dramatically.

I brought up the darned discussion in the first place because there are 
many people here way smarter than me,  and I was hoping for their input 
from a fresh look at the issues involved.




Please respond to MIDRANGE-L@midrange.com
Sent by:        owner-midrange-l@midrange.com
To:     MIDRANGE-L@midrange.com
cc: 

Subject:        Re: 4 - subfiles


Booth,
OK. Thats cool for small files. If I have 100,000 customers I'm not to 
sure about response time waiting to load the subfile. I've been following 
this thread and was really wondering about people saying they have no 
problem loading 2500 - 10000 records in a subfile and then displaying it. 
I know the RISC boxes are fast, but i was always taught to keep the i/o to 
minimum between displaying screens. I guess I have a hard time believing 
that this is not true anymore. (That's why we gave up on the scroll bar in 
the first place)
Ron


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---