Wrox Programmer Forums
Go Back   Wrox Programmer Forums > Microsoft Office > Access and Access VBA > Access
| Search | Today's Posts | Mark Forums Read
Access Discussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
  #1 (permalink)  
Old October 9th, 2004, 06:26 PM
Authorized User
Join Date: Jun 2004
Location: , , .
Posts: 55
Thanks: 0
Thanked 0 Times in 0 Posts
Default Windows XP ( +access 2003) problem?

Hi experts!

when I tried to update/insert a record in a table I got the
folowing an error written below. There is no error in my code. The same code was working on windows 2000 pro. what could be the problem in windows xp pro???????

Colud you please help me. Thank you in advance!

Server Error in '/' Application.

Operation must use an updateable query.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.OleDb.OleDbException: Operation must use an updateable query.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>


2) Add the following section to the configuration file of your application:

       <compilation debug="true"/>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.


  #2 (permalink)  
Old October 11th, 2004, 09:19 AM
Authorized User
Join Date: Jul 2004
Location: cleveland, oh, USA.
Posts: 66
Thanks: 0
Thanked 0 Times in 0 Posts

that usually means that there is no primary key defined. Jet requires a PK for positioned updates. If you are trying to update from a query, the underlying/updated table is the one that will require the PK.

Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem with Reporting Services and Windows 2003 ns_nataly Reporting Services 2 February 7th, 2007 06:29 PM
Access hosted on windows server 2003? hapsmack Access 1 July 11th, 2006 12:16 AM
ACCESS 2000 Report problem on Windows 2003 scourge Access 1 April 19th, 2006 05:36 AM
HELP - Access 2000 Runtime w Windows XP Compiled.. chasidim Access 2 April 3rd, 2006 11:06 AM
Access and windows 98 versus XP Bassamsater Access VBA 11 September 17th, 2003 11:29 AM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.