%META:TOPICPARENT{name="ErrorMessagesC"}%
==Error Messages (C)==

[[UDAErrorMessages|A]] [[ErrorMessagesB|B]] [[ErrorMessagesC|C]] [[ErrorMessagesD|D]] [[ErrorMessagesE|E]] [[ErrorMessagesF|F]] [[ErrorMessagesG|G]] [[ErrorMessagesH|H]] [[ErrorMessagesI|I]] [[ErrorMessagesJ|J]] [[ErrorMessagesK|K]] [[ErrorMessagesL|L]] [[ErrorMessagesM|M]] [[ErrorMessagesN|N]] [[ErrorMessagesO|O]] [[ErrorMessagesP|P]] [[ErrorMessagesQ|Q]] [[ErrorMessagesR|R]] [[ErrorMessagesS|S]] [[ErrorMessagesT|T]] [[ErrorMessagesU|U]] [[ErrorMessagesV|V]] [[ErrorMessagesW|W]] [[ErrorMessagesX|X]] [[ErrorMessagesY|Y]] [[ErrorMessagesZ|Z]] [[ErrorMessagesSymbols|#]]

    
===Could not process object '{{{<object>}}}'. The OLE DB provider 'MSDASQL' indicates that the object has no columns. (7357)===


Microsoft's Linked Servers return "Could not process object" errors, when users run UPDATE, INSERT, or DELETE statements in conjunction with <nop>OpenQuery (). Microsoft's <nop>OpenQuery function expects a result set. However, these statements do not produce result sets, when used with <nop>OpenQuery.

If you experience this problem, go to the following address:

http://support.microsoft.com/support/kb/articles/Q270/1/19.ASP

Microsoft provides a workaround and additional information.
    
===Evidence===

ODBC Client Trace