MS Access databases growing endlessly

[rocas]

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

[Colin Angus Mackay]

rocas wrote: Has anyone had a similar problem with Access databases? Sounds like normal database behaviour to me. As you perform actions on a database it creates transactions so that the database will be in a consistent state should anything go wrong. These transactions will be appended to the end of the file until you clear out the transaction log, in this case by running "Repair and Compress".

---

My: Blog | Photos | Next SQL Presentation WDevs.com - Open Source Code Hosting, Blogs, FTP, Mail and More

[Desi Bravo]

I had no problems in accessing information via Access Database using VB.Net. I created several datagrid programs accessing the MS Access database without an exception. I am just having problems in authenticating a login page that I am trying to use to open a secured program, that continues to point to the ExecuteReader being closed. bravo659

[rocas]

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"?