I am trying to solve a problem where a front-end MDB file grows and grows
until eventually it exceeds 2 gigabytes and crashes. Compacting and
repairing
slows the growth only slightly.
My client is running a small Access system on a network. The front-end MDB
file is about 2,500k and the back-end is 26,900k located on another
machine
in the network. The front-end database consists only of queries, forms,
re****ts and Visual Basic modules. All tables are defined as links to the
back-
end system. It does not hold any data in tables.
The front-end database sup****ts an estimating and quoting system with
little
data capture. It sup****ts complex searches into the back-end database to
interrogate previous quotations, product files etc. The quoting system was
created in Visual Basic by a developer who used techniques that I do not
fully understand.
Is it possible that the Visual Basic code is creating arrays or tables
that
are not cleared, and that are stored ***ulatively in the MDB file?
Until I find a more elegant solution, I am keeping an "original" copy on
the
front-end database and periodically copying it over the growing file. By
the
way, is there a method of reinstating this file automatically at end of
day?
This problem persists whether I use Access 2000 or Access 2007. It also
persists when the database is stored in 2000, 2002-3 or 2007 format.
I would love to hear from anyone who might have suggestions.
--
Message posted via http://www.accessmonster.com
|
