Re: What triggers import wizard to select 'BLOB' type?

Thanks, Lars, for the quick response;

In this case there was a lurking unmatched quote that I hadn't found before that was causing the columns to get smashed together, leading the wizard to conclude it had a field longer than 5000 characters, hence the BLOB choice.   So by resolving those un-escaped characters the issue was resolved; the proper NVARCHAR field is large, but not that large.

However, that highlights another problem/bug/feature:  The SQL IMPORT command seems to be ignoring my "optionally enclosed by" clause.  However I want to do some additional diagnosis before declaring it an actual problem.

Donn