On Mon, Feb 13, 2012 at 10:16 AM, Dave Crozier <[email protected]> wrote: > Stephen, > It would seem to be the new 10.0 client that is causing the problem. > Reverting to the standard preinstalled SQL Driver sorts the problem out so at > least I know now that the database integrity is intact which was my main > concern. > > There is obviously a setting in the new driver that is stopping the app > seeing the blob data correctly so I'll investigate more but the problem is > now not so urgent. The main problem with the old drivers is that they don't > support the failover which is why I am doing all this data transfer as we > have two servers now mirrored which at least I can now use, albeit only with > manual failover until I sort out this problem.... but at least I have a > working system and not 500 people baying for blood because all their document > scans and pictures have disappeared!!! > > I'll keep you all posted. > ----------------
Was the client updated to be referenced in the connection string? I was guessing YES otherwise it would not have received any data, and you are only having a problem with varchar(max) data. If the former client works keep using it! ;-> -- Stephen Russell 901.246-0159 cell _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cajidmyjkfe2ocpvknmxt+kbpmxzf856lrsobvdfa6jmtxww...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
