I thought of the same explanation. But how can I solve this problem. Is there an option for the connectstring that I can use to disable the log, or a method to programmatically call "Repair and Compress"?

Hello everybody, I have wrote a database application that connects via ODBC to MS Access databases. After running many SQL queries on the databases, their size grows considerably (a 320kb file can grow to MB sizes). If I run the 'Repair and compress'-operation in Access, the databases shrink back to their expected size. I tried switching from ODBC to OLEDB, but the problem remained unsolved... Has anyone had a similar problem with Access databases? I'd really appreciate if you could help me solve this problem. Thanks, paul