Craig,

Thanks for your ideas sir. They are valuable.

Currently, I still use one single Data Entry Form class - whether it be DBF tables or DE class with CA cursors. So, for my DE Class, it loads up the entire table from, say, the INVOICES table! Speed was pretty good initially, but when the app's Invoice records reached 100,000s, it now takes quite a few seconds of time to load up the data entry form. Hence, this thread.

Initially, my idea was to get the records in batches of X rows - akin to how web pages do it.

But, thanks to your advise, I will be refactoring my classes in that direction.

Dennis