I working on an existing app that uses DAO to connect to Access
databases. I am trying to update this app to allow the use of SQL
Server databases. At one point, we create a TableDef object for one of
the tables, then loop through the fields, looking at the TableDef.Type
with a Case statement and then acting accordingly. The problem is, the
TableDef.Type for SQL Server fields is not the same as for the Access
fields. So, I began debugging the code to get the values, but the
problem is that the Type is inconsistent. Nvarchar fields have a
TableDef.Type of 56 when running the program one time, but other times
have types of 57, 62, 60, etc. Is there a reason these are not
consistent? Is there a range of values that the types fall into? I'm
looking for a resource that shows the TableDef.Type values for SQL
Server field datatypes. Anyone know where I can find this?

Consider using ADO rather than DAO. DAO was superceeded back in 98, and the
documentation on MSDN is spotty.
http://msdn.microsoft.com/library/de...essingdata.asp

"Sean" <nbSean (AT) gmail (DOT) com> wrote

Unfortunately, this is not an option. I am adding changes to an
existing app, and cannot change to ADO.

Well, loop through the entire table and collect every distinct value of
TableDef.Type that DAO returns for the column, and perhaps it will distill
down to a specific few. Also, if the other data types, such as Int or char,
are consistent, then perhaps code your select.. case.. in such a way that
otherwise is assumed to be nvarchar.

Are you sure it's not the data length that being returned?

"Sean" <nbSean (AT) gmail (DOT) com> wrote

Ok, all other types of fields (bit, number, etc.) are consistent, the
text fields (nvarchar, ntext, etc.) are not. So, I took your
suggestion and put the text logic under the Case Else. This seems to
be the only workaround. Thanks for your help.