I never resolved it. I worked around it.

Instead of using data access of 'Table or View' in the data source, I used 'SQL command' with the command = 'select *...

Hi Gerald,

The default ProviderDescriptors.xml for ODBC is:

<dtm:ProviderDescriptorSourceType="System.Data.Odbc.OdbcConnection">

<dtm:SchemaNames

TablesSchemaName="Tables"

ColumnsSchemaName="Columns"

ViewsSchemaName="Views"

/>

<dtm:TableSchemaAttributes

TableCatalogColumnName="TABLE_CAT"

TableSchemaColumnName="TABLE_SCHEM"

TableNameColumnName="TABLE_NAME"

TableTypeColumnName="TABLE_TYPE"

TableDescriptor="TABLE"

ViewDescriptor="VIEW"

SynonymDescriptor ="SYNONYM"

NumberOfTableRestrictions="3"

/>

<dtm:ColumnSchemaAttributes

NameColumnName = "COLUMN_NAME"

OrdinalPositionColumnName="ORDINAL_POSITION"

DataTypeColumnName = "TYPE_NAME"

MaximumLengthColumnName = "COLUMN_SIZE"

NumericPrecisionColumnName = "COLUMN_SIZE"

NumericScaleColumnName = "DECIMAL_DIGITS"

NullableColumnName="NULLABLE"

NumberOfColumnRestrictions="4"

/>

<dtm:Literals

PrefixQualifier="""

SuffixQualifier="""

CatalogSeparator="."

SchemaSeparator="."

/>

</dtm:ProviderDescriptor>

The original error message complained about ORDINAL_POSITION, COLUMN_SIZE (twice) and DECIMAL_DIGITS....

Hi Nigel,

The customer is seeing the problem in VB.

I checked the data in QA to confirm what the customer has seen.

I have now looked at the VB code, rather than...

I Agree with ProfPylons.

Any action within a transaction will be observed to have worked within the transaction before you commit.

Is there a compination of TRANSACTION ISOLATION LEVEL and lock hints...

Looking at the syntax both should fail.

1) Has an extra comma

2) Has no closing parenthesis

When I tried it in QA, 1) worked but 2) failed?

Therefore the given answer is wrong.

Does...

That was my impression too.

It must have been a misprint.