Re: ADOX vs OleDB for DDL of new Procedure objects
- From: v-kevy@xxxxxxxxxxxxxxxxxxxx (Kevin Yu [MSFT])
- Date: Fri, 22 Apr 2005 02:55:29 GMT
Hi,
Your .NET code doesn't work because GetOleDbSchemaTable returns a table
which contains information of the current database. Modifying that table
will not update the database.
As Cor suggested, if you need to create a procedure in the mdb database, we
have to use CREATE PROCEDURE. You can use the same code as Cor has
provided. Just change the CREATE TABLE statement to CREATE PROCEDURE ......
HTH.
Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."
.
- Follow-Ups:
- Re: ADOX vs OleDB for DDL of new Procedure objects
- From: smitty_one_each
- Re: ADOX vs OleDB for DDL of new Procedure objects
- References:
- ADOX vs OleDB for DDL of new Procedure objects
- From: smitty_one_each
- Re: ADOX vs OleDB for DDL of new Procedure objects
- From: smitty_one_each
- ADOX vs OleDB for DDL of new Procedure objects
- Prev by Date: RE: Chlid rows of a datarow
- Next by Date: distributed transaction
- Previous by thread: Re: ADOX vs OleDB for DDL of new Procedure objects
- Next by thread: Re: ADOX vs OleDB for DDL of new Procedure objects
- Index(es):
Relevant Pages
|