Adobe Dreamweaver CC 2014 v.13 User Manual
Page 650
a SQL account of the same name, it will fail. Map any account that uses an underscore to an account name on SQL that does not use an
underscore.
[Reference]80004005—Operation must use an updateable query
This error occurs when an event is updating a recordset or inserting data in a recordset.
Here are possible causes and solutions:
The permissions set on the folder containing the database are too restrictive. IUSR privileges must be set to read/write.
The permissions on the database file itself does not have full read/write privileges in effect.
The database might be located outside the Inetpub/wwwroot directory. Though you can view and search the data, you might not be able to
update it unless the database is located in the wwwroot directory.
The recordset is based on a non-updateable query. Joins are good examples of non-updateable queries within a database. Restructure your
queries so they are updateable.
For more information on this error, see “PRB: ASP ‘Error The Query Is Not Updateable’ When You Update Table Record,” in the Microsoft
Knowledge Base at
.
[Reference]80040e07—Data type mismatch in criteria expression
This error occurs when the server tries to process a page containing an Insert Record or Update Record server behavior, and the server behavior
attempts to set the value of a Date/Time column in a Microsoft Access database to an empty string ("").
Microsoft Access has strong data typing; it imposes a rigorous set of rules on given column values. The empty string value in the SQL query
cannot be stored in an Access Date/Time column. Currently, the only known workaround is to avoid inserting or updating Date/Time columns in
Access with empty strings ("") or with any other value that does not correspond to the range of values specified for the data type.
[Reference]80040e10—Too few parameters
This error occurs when a column specified in your SQL query does not exist in the database table. Check the column names in your database
table against the SQL query. The cause of this error is often a typographical error.
[Reference]80040e10—COUNT field incorrect
This error occurs when you preview a page containing an Insert Record server behavior in a web browser and try to use it to insert a record in a
Microsoft Access database.
You might be trying to insert a record into a database field that has a question mark (?) in its field name. The question mark is a special character
for some database engines, including Microsoft Access, and should not be used for database table names or field names.
Open your database system and delete the question mark (?) from the field names, and update the server behaviors on your page that refer to this
field.
[Reference]80040e14—Syntax error in INSERT INTO statement
This error occurs when the server tries to process a page containing an Insert Record server behavior.
This error typically results from one or more of the following problems with the name of a field, object, or variable in the database:
Using a reserved word as a name. Most databases have a set of reserved words. For example, “date” is a reserved word and cannot be
used for column names in a database.
Using special characters in the name. Examples of special characters include:
. / * : ! # & - ?
Using a space in the name.
The error can also occur when an input mask is defined for an object in the database, and the inserted data does not conform to the mask.
To fix the problem, avoid using reserved words such as “date”, “name”, “select”, “where,” and “level” when specifying column names in your
database. Also, eliminate spaces and special characters.
See the following web pages for lists of reserved words for common database systems:
Microsoft Access at
Microsoft SQL Server at
MySQL at
[Reference]80040e21—ODBC error on Insert or Update
This error occurs when the server tries to process a page containing an Update Record or Insert Record server behavior. The database cannot
handle the update or insert operation the server behavior is trying to perform.
643