>Because Rod is sensitive? Seriously, have no idea. I certainly didn't intentionally flag the message ( to all ) in any way. How do you know a message is marked as a sensitive message?

LOL! It displays "sensitive message" in red under the Message ID, but it's no longer marked that way. I believe the UT staff marks messages this way. They also, apparently, took the flag off. I thought that they flag messages as "sensitive" if they contain something that might be considered objectionable to some people. That's why I wondered what the heck it was that you had posted!! <g>

Does anybody know what happened here?

~~Bonnie


>
>>Do you (or anyone) know why your previous post to Rod was marked as a "sensitive message"????
>>
>>~~Bonnie
>>
>>
>>>Hey Rod -
>
>>>
>>>Merry Christmas. Hope life is treating you well.
>>>
>>>I hadn't tried it until you suggested it - kind of liked the OLEDB - but just now I found ODBC will work - the driver is the .net odbc connection or something like that. The only problem is you have to write a query to get the data, so it is not nearly as slick as the OLEDB which lets you select all the tables you want to import. ( of course this may be SSIS vs DTS rather than OLEDB vs ODBC as this is the first time I'm trying to upsize DBFs into SQL 2005 using my favorite method in 2000 )
>>>
>>>Would be interested to know if there is any known incompatibility with SQL 2005 and the VFE OLEDB provider though. Seems like kind of a big deal so I have to assume it is something I am doing wrong or *somebody* would have noticed this before.
>>>
>>>Please let me know if you hear anything.
>>>
>>>all the best in the new year
>>>
>>>
>>>
>>>>Hey Chuck
>>>> I know this doesnt answer the question directly. But have you tried the ODBC driver ?
>>>>
>>>>Rodman