same database - grow to different sizes on two computers

[Simon]

I have an Access database with lot of data (about 200M of initial size). I
use a function with a loop to update each record in a big table. On one
machine (say A), error always occurs as the database size grows beyond 2G on
the half way of the run.

I placed the database on the other machine (B) which has exactly the same
system setting. It runs fine, and the final size is below 1G. What could
cause the difference?

Thanks.

 

[Joseph Meehan]

I have an Access database with lot of data (about 200M of initial
size). I use a function with a loop to update each record in a big
table. On one machine (say A), error always occurs as the database
size grows beyond 2G on the half way of the run.

I placed the database on the other machine (B) which has exactly the
same system setting. It runs fine, and the final size is below 1G.
What could cause the difference?

Thanks.

Older versions of Access have a 1 gig size limit and newer ones have a 2
gig limit.

 

[Arvin Meyer [MVP]]

Looping through recordsets, updating data increases bloat over other update
methods, like a thraight SQL update query. That said, it can also be the
indexes creating the bloat. If you change your code to drop the indexes, run
the updates, compact the database, then reapply the indexes, (then compact
again if you'd like) it should run faster, and bloat less.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads:
http://www.datastrat.com
http://www.mvps.org/access