I doubt this is a bug at all, because I don't think that SQL even defines
such a concept as "column order". Whenever I use the Oracle ODBC driver with
Access 97 though, the columns come back in exactly the order I defined them,
so I'm not sure how your environment is acting differently.
Brad Pybus <brad_pybus_nospam_at_hotmail.com> wrote in message
news:GgY63.825$VN.6865_at_client.news.psi.net...
> Here is my situation. I use SQL server to as a back end to MSAccess as a
> front end. When I open tables with MSAccess, the field order directly
> corresponds to the order of the fields in the original SQL server create
> table statement. We had a convention where the first field was ALWAYS the
> primary key for the table. The code we have in MSAccess works based on
this
> convention. In other words we do things like:
>
> fldPrimaryKey = MyTableDef.Fields(0)
>
> But now that we have ported the database over to Oracle and connected to
> Access via the Oracle ODBC driver, when I open a table in Access, the
field
> order does not correspond to the field order in the original create table
> statement.
>
> Is this the Oracle ODBC driver's fault?? Is there any way to get it to
> transmit the fields in the correct order?
>
> We already have one fix for this problem:
>
> ' Where GetPrimaryKeyField() iterates through the indexes
> ' collection to find the primary key field
> fldPrimaryKey = GetPrimaryKeyField(MyTableDef)
>
> -----------------------------------
> We would rather figure out how to get the ODBC driver to transmit the
fields
> in the correct order. Any suggestions?
>
>
> Thanks,
> Brad
>
> --
> To reply to me, remove the "_nospam" from my address.
>
>
Received on Mon Jun 07 1999 - 18:22:46 CDT
