Hi Evan;
Your suggestion( it was also my first thought ) was passed to the client last night when I was there to fix the problem, and rejected. In total there are over 900 jpegs in the database, distributed in two tables(600 item, 300 donors). 1000 if I count another table that is not part of the problem set(Club members).

It does work, provided there is about 1gb swap space available, and moving through the view is quick, once it loads.

The client rejected it becuase all of the photo editing is done in place on the data entry screens, including the initial load from the camera. For computer savvy folks, it would not be a problem, but some of the apps users only use a computer once a year, and the app they use is this app.

If all else fails, I might have to move the photos to the file sys and link the filename to the tables, but that will only get me a t'd off client. I would realy prefer to limit pre-fetching to about 10 records at a time.