ADO Execute

nathansav

Registered User.
Local time
Today, 08:07
Joined
Jul 28, 2010
Messages
114
Hi,

I have written a tool in Excel VBA that compares an old copy of a database, to the new copy.

Any static tables are removed and added from the old.

So in the new i use connNEW.Execute "drop table x"
and then in the old i use a SQL insert into
so connOLD.Execute "Select x.* into db2 ..." etc

this all works fine, but i get bloating, when i do the execute, i am using the noRecords argument to.

Can anyone advise?
 
No clue what you are asking: what exactly do you do to old db, to new db and where is the bloating and is that a problem?

Remember we do not read minds but only have the info YOU supply!
 
I thought the SQL would have given it away from the OLD connection i am doing an insert into db2, which bloats.
 
Its obvious it will bloat, dropping a table and adding a new one will cause blaot unless you compact the database afterwards which can be done via command line if you so desire.

No way to avoid/prevent the bloat, only clean it up afterwards.
 
Hi namliam, thanks for that, its what i thought, i thought there may be a way of sorting it out.

That's the approach that i have used, apart from the user to open and close (compact on close) as the final step of the DB installation.

Thanks

Nathan.
 

Users who are viewing this thread

Back
Top Bottom