You can't.  Access was only designed originally to house small to medium 
numbers of records with about 25 concurrent users.  Your best best would 
be to get hold, of a copy of msde SQL Server.  This will be the only way 
around your "size" problems.  I have had this issue with Access for many 
years and the only way to keep your databases small is to make sure that 
you don't over use indexes.

Probably doesn't help much but MSDE Sql Engine is free from Mirosoft.

Ben

> Hi,

> I am currently writing a vb app to perform various data processing tasks 
t> hat we use.  One such task is to create two fields on an Access 2000 
d> atabase, a 'TABLE' and an 'ID' field.  Both are text and are created 
u> sing ADOX which I do not have any problems with.

> the problem I get occurs when I populate these fields using an ADO 
r> ecordset.  I have tried various types of recordsets/locking but to no 
a> vail.  My current set up is to open an OLEDB connection string to the 
d> atabase, then open a recordset returning both of the new fields.  I 
s> croll down each record populating each field accordingly.  This all 
w> orks without a problem but the database size increases massively.

> My current example is a single table of 17778 records whereby the 
d> atabase increases from 4072 to 75208KB (over 18x!!!)...

> I can compact/repair the database which reduces it well enough but when 
I 
a> m working with hundreds of thousands of records the processing power is 
g> reatly reduced and the compacting procedure takes an awfully long time!

> Any suggestions as to how I may prevent access from increasing so muxh 
w> ould be gratefully received.

> Kind regards,

> Carl Howarth
C> arlHowarth@n...