Very Computer

It all works fine if i create a column with (for instance) the adInteger
type instead.

Here is the code:

-------
Private Sub Command1_Click()

Dim CnTo As New ADODB.Connection

Dim XCatalog As New ADOX.Catalog
Dim XTable As New ADOX.Table
Dim XColumn As New ADOX.Column

CnTo.Open "Provider=SQLOLEDB;User Id=sa;Initial Catalog=test1"

'Reference to the catalog
Set XCatalog.ActiveConnection = CnTo

'Create New Table
XTable.Name = "NewTable"
'Create New column
XTable.Columns.Append "NewColumn", adTinyInt
'Now Append the table (this gives the error)
XCatalog.Tables.Append XTable

End Sub
--------------------

Helps appreciated.

Fabio Pagano

Just my option, of course.

Richard

Thanks to the authors of www.able-consulting.com/ADODataTypeEnum.html

Fabio Pagano

Quote:Fabio Pagano wrote...
>I am creating a new table in SQLServer 7.0 using ADOX 2.1 from VB6. When i
>try to create a column of type adTinyInt, the program causes the following
>error in the Catalog.Tables.Append method:
>Run-time error '-2147217859 (80040e3d)': a specified type was invalid

>It all works fine if i create a column with (for instance) the adInteger
>type instead.

>Here is the code:

>-------
>Private Sub Command1_Click()

>Dim CnTo As New ADODB.Connection

>Dim XCatalog As New ADOX.Catalog
>Dim XTable As New ADOX.Table
>Dim XColumn As New ADOX.Column

>CnTo.Open "Provider=SQLOLEDB;User Id=sa;Initial Catalog=test1"

>'Reference to the catalog
>Set XCatalog.ActiveConnection = CnTo

>'Create New Table
>XTable.Name = "NewTable"
>'Create New column
>XTable.Columns.Append "NewColumn", adTinyInt
>'Now Append the table (this gives the error)
>XCatalog.Tables.Append XTable

>End Sub
>--------------------

Kirk Allen Evans

Quote:> I don' have a problem using SQL to create tables with tinyint fields,
I've
> had problems with ADOX in many other places (such as creating date
fields
> when reading a date field from a Jet 351 database, type missmatch.)
I have
> a funny feeling ADOX is not there yet.  It seems to me, and this is
just my
> opinion, that when ADO 2.0 came on the scene everyone complained
there was
> no syntax to manipilate database structure with ADO, so MS quickly put
> together ADOX and shipped it with ADO 2.1.  I always wondered why
ADOX is a
> separate COM than ADO.  Whay was it not part of ADO like DAO?

> Just my option, of course.

> Richard

(Do not send mail to the Deja News account used

Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.