Hi,

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

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

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

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

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

Kind regards,

Carl Howarth
CarlHowarth@n...