i have legacy vb6 monolithic application reads/writes/deletes records access database using ado library functions. there many connections made in multiple functions single database:
despite fact data in db not large, access mdb file grows rapidly leading hit 2 gb mark. way out me stop application, compact , repair db , restart app. creating many connections application cause issue? way resolve this?
as per @plutonix, data manipulation operations expand db. call "not large". mdb >100mb large!
it sounds it's time scale out application use linked tables , store data in sql server instance (express free). leaves application logic in ms access. doing requires minimal effort , keep almost of code without touching it.
Comments
Post a Comment