[Steve_Haley]

The other thing that will help is to fully close the app (double tap home button then swipe it away) after transferring each 1000 books. The app performs some maintenance on the database at start-up which will help; this only takes a few seconds to do.

There are two problems happening at the same time: (1) the app used to run out of RAM during book transfers. For me, when transferring 1000 books, the app used to use about 120mb and now it only uses about 50mb. This problem manifested itself by the app abruptly crashing (returning to the home screen of the iPad without notice) during book transfers. This really should happen a lot less now.

(2) the database file itself could get too large. This one hasn't been fixed quite as nicely, since it requires the app to be restarted, as mentioned above. However, it should still help; for me, my database file reached approximately 800mb after transferring 1000 books, and then after restarting, the new maintenance code reduced it down to 50mb. Different devices have different limits, but it seems that if the app is launched with a database of between 2 and 4gb, the database corrupts and gets reset. So it's a bit of a pain, but as long as you restart the app between sending batches of 1000 books, you should be able to get further.

(And yes, figuring out a better way of handling this is still on my list!)