Urgent Advice for Display of Records In VB

[Guest_imported]

One of VB application we are encountering a problem, any suggestions or help is really appreciated.

We are looking for alternative solutions to display records in VB either using of the following if possible?
a) ARRAYS
b) Grid
c) Spread Control. Max limitation 60,000 records

Our VB application calls RPC in CICS region, which process data and creates a VSAM dataset.The volume of data that is processed is HUGE say ranges from 7 to 20 million records and can go high at a later date say to 25 million. Then the process data is viewed, the VSAM dataset is read and data is sent to VB and in turn displays the content on the screen.

Currently we are using GRID control which displays 2000 records. As per our knowledge Grid control as a limitation of 2000 records.

We would like to display the huge volume of data in small segments say 1000 records at a time, if yes what approach we should follow to resolve our problem? For example : A given treaty has generated 7 million records and we display to the user in smaller portions?

What is the capacity of an array in VB is there a default limitation?

If the array size based on the Memory of the machine?

If an array can HOLD million records and then display 1000 records at a time --- i.e. page 1, next 1000 records page 2. next page 3 so like this how many Grids can we have? Is there a limitation of the GRID? meaning 7 - 8 million records can run into PAGES.
Can we swap 'NEXT' or 'PREVIOUS' as we do in HOTMAIL.

 

[Durkin]

I think this is the third thread in which you have asked this question and the other twice you were asked why you want to display millions of records and you haven't replied. This is not just idle curiosity on the part of the respondents. It seem unrealistic to expect any user to have to list through 7-20 million records. Therefore, it's possible that you are looking for records that fit some specific criteria which could cut down the number of records. If you do have to go through all the records, there is probably no need to have all 7 million records in memory at the same time. You could hold a reasonable amount in memory and then if you needed to view a different part of the data you could release the currently held data and load up the new.
I'm not sure what you mean when you say your VB application calls RPC in CICS region, which process data and creates a VSAM dataset. If you can't access the data in small chunks this way perhaps you should have a database on a server in the middle to temporarily hold the data to be accessed in manageable amounts by the client machine.
Anyway, I still can't imagine why anyone would want to scroll through 7 million records, so if you want to shed some light on the subject, please do. Durkin
alandurkin@bigpond.com