Hi, Our development team has to insert about 42 rows into a database table. We have used beans and set and get properties using class ID = r. But we're facing an error "Operation must use an updateable query." Can someone figure out what's wrong and help us? Thank you! The code is below: <%@ page import="java.sql.*" %> <%@ page import="java.util.*" %> <%@ page import="java.io.*" %> <jsp:useBean id="r" class="Resume" scope="request"/>
The sql query have to be in a single line. The query have be same order of the database..attribute. I have the same problem before.. I chage the structure now it works fine for me.. Thanks Shankar. ------------------
1. The most common reason is that the Internet Guest account (IUSR_MACHINE), which is by default part of the "Everyone" group, does not have Write permissions on the database file (.mdb). To fix this problem, use the Security tab in Explorer to adjust the properties for this file so that the Internet Guest account has the correct permissions. NOTE: When using Microsoft Access databases with ADO, it is also necessary to give the Internet Guest account Write permissions on the directory containing the .mdb file. This is because Jet creates an .ldb file to handle database locking. You may also need to give read/write permission on the "Temp" folder because Jet may create temporary files in this directory. 2. A second cause of this error is that the database was not opened with the correct MODE for writing. If you perform the Open on the Connection object, you use the Mode property to indicate the permissions on the connection as shown here:
NOTE: By default, the MODE is set to 0(adModeUnknown), which generally allows updates. 3. Another cause of this error is that the "Read Only" setting may be checked in the Options page for this DSN in the ODBC Manager. 4. The last issue and work around pertains to any SQL data source. The error can be caused by SQL statements that violate referential integrity of the database. Here are a few of the most common queries that fail: - The simplest group to deal with are those you cannot change: crosstab, SQL pass-through, union, or update (or make-table) action queries that have UniqueValue properties set to Yes. - Another very common cause is when the join includes linked ODBC tables that do not have unique indexes. In this case, there is no way for SQL to guarantee that records are unique in a table that has fields whose value will change with the query. - One cause does have a robust workaround. If you try to update a join field on the "one" side of a "one-to-many" query it will fail unless you turn on cascading updates. This way, you delegate referential integrity to the JET engine."
[ February 06, 2003: Message edited by: Amol Khiste ]
My pie came with a little toothpic holding up this tiny ad:
create, convert, edit or print DOC and DOCX in Java