🚀 go-pugleaf

Not 100% sure here but you might try having a look at Compacting and
Repairing your database.  Try it from within MS Access first, on the
oversized table i .e. Open 'Big' Database, Tools->Database
Utilities->Compact and Repair Database.

Don't really know why this should happen, but if performing a C&R operation
resolved your problem then drop me an e-mail and I can send you a code
snippet to perform this operation under C++Builder.

By the way, are you creating your table from within Builder, via an ADO
connection?  Is so, how?  I would like to see the code if possible.

HTH,

Mike C

"Mike Ruskai" <spamten.knilhtrae@begonedynnaht.net> wrote in message
news:gunaalqrneguyvaxarg.h5ezqm0.pminews@207.105.83.65...
> I've discovered that a table created via SQL through ADO ends up being
twice
> the size of one created in Access.
>
> The table definition looks identical in Access, but the packed database
size
> is twice what it should be, with nothing but the table (with no indexes
added
> yet).
>
> This has a very real (and very adverse) effect on performance whenever
> indexes aren't used.
>
> If I create the empty table in Access, and fill it up with a program via
ADO,
> the size is normal.  So it's not writing data with ADO, it's just creating
> the table.
>
> If I export that table from Access to another Access database, it's still
> twice the normal size.  If I copy and paste the table structure in Access,
> whatever it is that causes a bloated table is copied as well.
>
> Anyone have any idea why this happens?
>
>
> --
>  - Mike
>
> Remove 'spambegone.net' and reverse to send e-mail.
>
>