I wouldn't think DLL calling overhead would be significant when dealing with things as slow (relatively) as a database.
Is it really necessary for it to be a DLL? You might be able to statically link it and remove that overhead. Are you using COM or ActiveX to call it? If I remember right they had a lot more overhead than a vanilla DLL. Sounds like a job for the profiler! --- Chris Schirlinger <[EMAIL PROTECTED]> wrote: > > Hmmmm.... The fact that the freelist size is different > > suggests either a bug in sqlite3_analyzer or a corrupt > > database file. What does "PRAGMA integrity_check" say? > > It returned a batch of Page not used (from about 4 to 48 I think).\ > > That was it > > > What OS did you say you are using? > > Windows XP professional on both test machines > > We are currently examining the componants we are using to access > SQLite3. We are accessing the DLL more directly now through exported > DLL functions and getting better speeds > > > ===== --------------------------------- "Lord Tarlington gazed upon the crazed Egyptian hieroglyphics on the walls of the ancient tomb of the petrified pharaoh, he vowed there would be no curse on him like on that other Lord, unless you count his marriage to Lady Tarlington who, when the lost treasure was found, will be dumped faster than that basket in the bulrushes." Melissa Rhodes --------------------------------- The Castles of Dereth Calendar: a tour of the art and architecture of Asheron's Call http://www.lulu.com/content/77264 __________________________________ Do you Yahoo!? Yahoo! Mail - Helps protect you from nasty viruses. http://promotions.yahoo.com/new_mail
