Tech Support Forum - View Single Post

JeffPalmer · 10-02-2009, 11:55 PM

Thanks for the reply. I had already flagged the column as unique and as the primary index in Access when I designed the table.

The issue turned out to be that I was using TADOTable to access the database. This caused Delphi to cache the entire DB into memory. This wasn't a problem until I ran out of actual ram and started hitting swap memory, which ground the thing down to a very slow crawl.

The solution was to use TADOQuery instead. It didn't have quite the performance using TADOTable did when the table was small, but very acceptable performance, regardless of the size.

10-02-2009, 11:55 PM	#3 (permalink)
JeffPalmer Registered User Join Date: Jun 2009 Location: Los Angeles Posts: 2 OS: XP	Re: Delphi/Access Out of Memory Thanks for the reply. I had already flagged the column as unique and as the primary index in Access when I designed the table. The issue turned out to be that I was using TADOTable to access the database. This caused Delphi to cache the entire DB into memory. This wasn't a problem until I ran out of actual ram and started hitting swap memory, which ground the thing down to a very slow crawl. The solution was to use TADOQuery instead. It didn't have quite the performance using TADOTable did when the table was small, but very acceptable performance, regardless of the size.