recordset to adox table.

[Drew Curry]

After searching through the posts for "adox" it appears many folks are
struggling with this. I find myself in the same boat.

My problem:

Take an ado recordset, pass it to a function along with a table name,
and create a new table based on the fields in the rst. Seems simple
enough. Fighting the field to column conversion issues.

ADOX rears it ugly head and seems to make it very very hard. I am using
an Access2k mdb, ado2.5, adox2.5. Has anyone worked out this generic
routine and care to share some secrets.

I am trying to take the results of:

Set rst = cnn.OpenSchema(adSchemaProviderSpecific, , _
JET_SCHEMA_USERROSTER)

and push it to a table.... that is all..

thanks, drew..

[Mike]

Drew:

First, if you are using Access, you might want to consider using DAO. It
is written specifically for JET. ADO actually might give you performance
issues in a JET environment.

Getting to your specific question, use a MAKE TABLE query following your
SELECT. Do something like this:

SELECT field1, ... , fieldn
INTO tbl<TABLENAME>
GROUP BY | HAVING | WHERE clauses

This will work in DAO or ADO.

Hopefully this answers your question

Drew Curry <dcurry@no.spamola.home.com> wrote:
>After searching through the posts for "adox" it appears many folks are
>struggling with this. I find myself in the same boat.
>
>My problem:
>
>Take an ado recordset, pass it to a function along with a table name,
>and create a new table based on the fields in the rst. Seems simple
>enough. Fighting the field to column conversion issues.
>
>ADOX rears it ugly head and seems to make it very very hard. I am using

>an Access2k mdb, ado2.5, adox2.5. Has anyone worked out this generic
>routine and care to share some secrets.
>
>I am trying to take the results of:
>
>Set rst = cnn.OpenSchema(adSchemaProviderSpecific, , _
> JET_SCHEMA_USERROSTER)
>
>and push it to a table.... that is all..
>
>thanks, drew..

[Drew Curry]

Because of the seemingly unusual nature of the rst returned by
OpenSchema call, i resorted to created another regular adodb.recordset
and filling that with the OpenSchema rst, assigned the new rst to the
grid recordsource and everything is fine...

drew..
>
> Drew:
>
> First, if you are using Access, you might want to consider using DAO. It
> is written specifically for JET. ADO actually might give you performance
> issues in a JET environment.
>
> Getting to your specific question, use a MAKE TABLE query following your
> SELECT. Do something like this:
>
> SELECT field1, ... , fieldn
> INTO tbl<TABLENAME>
> GROUP BY | HAVING | WHERE clauses
>
> This will work in DAO or ADO.
>
> Hopefully this answers your question
>
> Drew Curry <dcurry@no.spamola.home.com> wrote:
> >After searching through the posts for "adox" it appears many folks are
> >struggling with this. I find myself in the same boat.
> >
> >My problem:
> >
> >Take an ado recordset, pass it to a function along with a table name,
> >and create a new table based on the fields in the rst. Seems simple
> >enough. Fighting the field to column conversion issues.
> >
> >ADOX rears it ugly head and seems to make it very very hard. I am using
>
> >an Access2k mdb, ado2.5, adox2.5. Has anyone worked out this generic
> >routine and care to share some secrets.
> >
> >I am trying to take the results of:
> >
> >Set rst = cnn.OpenSchema(adSchemaProviderSpecific, , _
> > JET_SCHEMA_USERROSTER)
> >
> >and push it to a table.... that is all..
> >
> >thanks, drew..
>
>