Skip to main content

I am sure the first few times I used my DSN with AcuXDBC version 10.3.1 driver 64bit the data from my vision file imported in the same order as the file definition (xfd).  Now everytime it is bringing it in with the column names shown alphabetical order which I do not want.

 

Any ideas?

I see also that MS Access still has 256 column limit?

 

I will try MS SQL server linked server so any recent documentation on AcuXDBC and linked servers in MS SQL would be handy.

 

Thanks

Jim 

I am sure the first few times I used my DSN with AcuXDBC version 10.3.1 driver 64bit the data from my vision file imported in the same order as the file definition (xfd).  Now everytime it is bringing it in with the column names shown alphabetical order which I do not want.

 

Any ideas?

I see also that MS Access still has 256 column limit?

 

I will try MS SQL server linked server so any recent documentation on AcuXDBC and linked servers in MS SQL would be handy.

 

Thanks

Jim 

Note that I have proved that the columns appear in the correct order by select * within ASQL query

I am sure the first few times I used my DSN with AcuXDBC version 10.3.1 driver 64bit the data from my vision file imported in the same order as the file definition (xfd).  Now everytime it is bringing it in with the column names shown alphabetical order which I do not want.

 

Any ideas?

I see also that MS Access still has 256 column limit?

 

I will try MS SQL server linked server so any recent documentation on AcuXDBC and linked servers in MS SQL would be handy.

 

Thanks

Jim 

Are you saying that using ODBC, the columns come back in alphabetical column name order but when using xdbcquery the columns come back in XFD order?

 

Pets:

ODBC:

ANIMAL_TYPE

BREED

OWNER_ID

PATIENT_ID

PATIENT_NAME

TREATMENT

 

ASQL:

PATIENT_ID

PATIENT_NAME

ANIMAL_TYPE

BREED

TREATMENT

OWNER_ID

Terms & ConditionsAccessibility statement