Re: Cannot insert or update columns from multiple tables (post #2) Need help please


Here is a really strange thing when I am using SQLOLEDB (Microsoft OLE DB
Provider for SQL Server) to update records from a dataset on a multi-tables
view containing an "instead of trigger". I am using a server-side cursor
(and I cannot use a client-side cursor in my case).

But if I change the SQL driver to use an ODBD DataSource (Microsoft OLE DB
Provider for ODBC Driver), is it working.

What is the problem with SQLOLEDB and I can I solve this issue?

Your problem seems to fit the description in this document
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B835677
--
Brian Bushay (TeamB)
Bbushay@xxxxxxxxx
.

Relevant Pages

  • Re: Cannot insert or update columns from multiple tables (post #2) Need help please
    ... message in the SQL Server trace file, it represents the issue is caused by ... fixed after changing to ODBC Provider, it seems the root cause is on the ... Please be conscient that I don't want to accuse Delphi or Microsoft, ... But if I change the SQL driver to use an ODBD DataSource (Microsoft OLE DB ...
    (borland.public.delphi.database.ado)
  • Re: Disabling ASP.net 2.0 Membership
    ... I checked out the article you referenced and implemented my own provider. ... as a FoxPro database, an Oracle database, or other data sources. ... custom connection string so that I can use the Commerce Server SQL Server ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ERROR: Provider Management - Could not establish a connection to t
    ... If you have not yet created the SQL Server database, ... Can any data provider be used to ... Exception Details: System.Data.SqlClient.SqlException: A connection ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: .NET data provider or OLEDB provider?
    ... >I don't see where you see a built-in query engine. ... >service provider, ... >OLE DB providers don't have to support SQL however, ... > SQL Server linked server, SQL Server can handle the queries. ...
    (microsoft.public.data.oledb)
  • Re: Need Help: Operating system error 3706
    ... Installing an additional component resolved the problem and the software is now able to connect to the database ... The developer is currently doing a complete rewrite/update of the program, including database functions. ... While this would require a modest re-write, it's not that tough to convert to a managed-code provider instead of the COM-based OLE DB provider. ... If the application is not based on .NET, then make sure the application is upgraded to use the SNAC (SQL Server Native Client) provider which is less trouble-prone than the older MDAC-based providers. ...
    (microsoft.public.sqlserver.connect)