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



This is from BOL:

VIEW_METADATA

Specifies that SQL Server will return to the DBLIB, ODBC, and OLE DB APIs
the metadata information about the view, instead of the base table or
tables, when browse-mode metadata is being requested for a query that
references the view. Browse-mode metadata is additional metadata returned by
SQL Server to the client-side DB-LIB, ODBC, and OLE DB APIs, which allow the
client-side APIs to implement updatable client-side cursors. Browse-mode
meta data includes information about the base table that the columns in the
result set belong to.

As you see it states that it will work for the client-side cursors only, but
not for the server-side one.

If you really just want to update some record/records through a View then
you could switch to TADOCommand with appropriate commandtext assigned to
appropriate update statement. Can you explain what you are trying to
accomplish and why you can't use client side cursors?


.



Relevant Pages

  • Re: SQL2005 sys tables
    ... system objects are stored in a new system database ... there is an equivalent catalog view for every system table. ... Another important change related to system metadata is that in SQL Server ...
    (microsoft.public.sqlserver.security)
  • Meta Data Cleanup options SQL Server 2008
    ... We are currently on SQL Server 2008 and have laptops that we transfer data to ... the best way to handle the metadata cleanup is by changing the subscription ...
    (microsoft.public.sqlserver.server)
  • SQLServer Fmtonly and ADO
    ... ADO uses FMTONLY ON to get metadata from sql server. ...
    (microsoft.public.data.ado)
  • Re: Difference between catalog and metadata?
    ... be stored in the catalog / metadata? ... DB2, Oracle, and SQL server all came into being before there was a standard ...
    (comp.databases.theory)
  • Re: Protecting database
    ... I meant the metadata is available to anyone who can connect! ... "Kalen Delaney" wrote in message ... > SQL Server MVP ...
    (microsoft.public.sqlserver.security)