Mike,
Yep, this is somewhat document in SQL Server 2000 BOL title "Filtering
Supported File Types" - "...the file extension must be stored in a separate
column on the table. This type column can be of any character-based data
type and contains the document file extension, such as .doc for a Microsoft
Word document. If the type column is NULL, the document is assumed to be a
text file (.txt)."
Although, in this newsgroup, it's been often posted that the file extension
column must be defined as char(3), char(3) or sysname, however, recent
testing with a SQL Server 2000 with SP3 applied provides hints that an
un-documented fix was done for this as I was able to get this to work with a
varchar(100) column datatype.
Regards,
John
> OK,
>
[quoted text clipped - 17 lines]
>
> <M>ike
<M>ike - 25 Jun 2004 09:02 GMT
I think my problem was that I previously had a char(16) as the field
datatype which included all those extra spaces!
> Mike,
> Yep, this is somewhat document in SQL Server 2000 BOL title "Filtering
[quoted text clipped - 38 lines]
> >
> > <M>ike