🚀 go-pugleaf

I use ADOX with MDAC 2.6 but I just use it to create the database (JET 4.0)
only because the CREATE DATABASE is not supported. I create the table(s)
with SQL - works a treat. How about just trying a shorter SQL string -
create less fields - and see if it works and if not post your SQL here?

Rgds,

Bob


"Mike Ruskai" <spamten.knilhtrae@begonedynnaht.net> wrote in message
news:gunaalqrneguyvaxarg.h2w4ig0.pminews@207.105.83.65...
> When I had MDAC 2.5 installed, I discovered that creating a table with
> Unicode compression via SQL was impossible (the "WITH COMPRESSION" key
words,
> though documented, were not implemented).
>
> So, I used ADOX to create the database and tables.  Worked fine.
>
> Now I've installed MDAC 2.7, and find that the ADOX method doesn't work
> anymore.  Everything seems to work - no error messages of any kind - but
the
> tables themselves are not created.  The call to Catalog->Tables->Append()
> does not throw an exception, and worked perfectly fine before, but now
does
> apparently nothing.  The tables are not created.
>
> To make sure I knew what I was talking about in another discussion, I
tested
> the "WITH COMPRESSION" key words with MDAC 2.7, since someone who posted
here
> said they work (which they don't, if using MDAC 2.5).  Sure enough, with
MDAC
> 2.7, Unicode compression via SQL is possible.
>
> So, I figure I'll just go back to the way I was originally going to do
it -
> create the table via SQL.
>
> But it doesn't work.  An exception complaining about field definition
syntax
> is thrown.  So, I cut and paste the (rather long) SQL string into Access,
and
> it points to the location of the error - using a type named BOOLEAN.  This
> appears, once again, to be a conflict between MS documentation and MS
code.
> BOOLEAN is documented as an alias for BIT, YESNO, etc.  If I replace
BOOLEAN
> with BIT, it works (minus WITH COMPRESSION, of course, because that still
> doesn't work in Access itself).
>
> Make the change in code, and find that I still get an exception.  I kill
the
> WITH COMPRESSION in code, try again, and get an exception.  I cut and
paste
> into Access, and the table is created.
>
> Anyone know why SQL would work in Access but not via ADO?  I even got rid
of
> the BIT type completely, replacing it with SMALLINT.  Made no difference.
>
> If necessary, I can post the entire SQL string, but it's a tad long (over
50
> fields are created).
>
>
> --
>  - Mike
>
> Remove 'spambegone.net' and reverse to send e-mail.
>
>