🚀 go-pugleaf

An example of what I'm about to describe is here:

<http://home.earthlink.net/~thannyd/ado/oddado.exe>

It's a self-extracting RAR archive of a sample program with all source. 
Modifications to the project file will likely be required to to build it
yourself.

I'm using BCB6 Pro.

After creating an Access database, there are two options for creating tables
- via ADOX, and via SQL.

I discovered a while back that using SQL results in a bloated table, which is
not the case when using ADOX.  

What I mean by bloated is that the resulting database, after being compacted,
is substantially larger.  With tables containing a couple hundred thousand
records, performance suffers considerably.

The example program referred to above creates two Access databases with an
example table, one for each table creation method.  After being automatically
compacted, the resulting size is reported.  

On my machine, which has MDAC 2.7 and Jet 4.0 SP8 installed, the DB created
using ADOX is 4,689,920 bytes, and the DB created using SQL is 7,376,896
bytes.  With 10,000 test records, the figures are 53,841,920 and 81,141,760,
respectively.

Any ideas on what exactly is going?

On other matter, anyone know why ADOX silently fails if you attempt to create
a field of type adBoolean or adTinyInt?

--
 - Mike

Remove 'spambegone.net' and reverse to send e-mail.