Re: Unable to update view in Sql Server 2000



fig000 (neilnewton001@xxxxxxxxx) writes:
> I have an application that's running fine on development servers (web
> and database-sql server 2000). I'm updating a record through a third
> party component but I don't think the component is the problem. What's
> happening is that I'm updating fields that are part of view. I'm only
> updating fields in one table of the view and this works fine in the
> development environment.
>
>
> What happens in the production environment when I try to update
> (using the third party component) I get the following message:
>
>
> "Current recordset does not support updating. This may be a limitation
> of the provider or of the selected locktype."
>
>
> As an experiment I took the same code but removed the view, leaving
> only the table I want to update as the record source. In that case the
> update worked. So it seems that something in the production database
> doesn't like me updating a view. However I can do that in the database
> in the development environment.
>
>
> The third party component is dbnetgrid which works fine in the
> development environment. I can only conclude it's something about the
> database that prevents me from updating this same table if it's in a
> view. I've talked to our DBA but he says there's no difference between
> the databases. Any ideas would be appreciated.

Unfortunately, this is difficult to answer without knowledge about
the submitted queries and the view and table definitions.

I guess the component submits the queries. To see what that is, you
cam use Profiler. However, this requires sysadm privileges, which I
assume that you don't have.

To compare the view table definitions, you can use sp_help, or script
them from Query Analyzer. Give particular attention to keys.

--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

.



Relevant Pages

  • Unable to update view in Sql Server 2000
    ... party component but I don't think the component is the problem. ... happening is that I'm updating fields that are part of view. ... So it seems that something in the production database ... The third party component is dbnetgrid which works fine in the ...
    (comp.databases.ms-sqlserver)
  • Re: SELECT COUNT(*) returning wrong value
    ... Next step I might take is to create a new database (preferably on a ... different server) and use DTS to copy those two tables over to it... ... If not, try updating ...
    (microsoft.public.sqlserver.server)
  • Updating Subsciber Replication Error
    ... an Updating Subscriber replication configuration. ... I can create a subscription to the second server. ... Could not locate entry in sysdatabases for database 'central' No entry ...
    (microsoft.public.sqlserver.replication)
  • Re: Server table not updating from linked workstation
    ... It sounds like your workstation is not actually linked to the shared ... Our problem is our back-end database on the server is not updating from ... Out tables are located on the server and our work stations are linked to ... Yet for some reason the server database is not updating. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: Updating Subsciber Replication Error
    ... I suspect that your Subscriber is having a hard time figuring out where the ... Looking for a book on SQL Server replication? ... > an Updating Subscriber replication configuration. ... > Could not locate entry in sysdatabases for database 'central' No entry ...
    (microsoft.public.sqlserver.replication)