Microsoft KB Archive/289317

= FP2002: Cannot Use the FrontPage Database Editor with Databases Created by FrontPage =

Article ID: 289317

Article Last Modified on 1/31/2007

-

APPLIES TO


 * Microsoft FrontPage 2002 Standard Edition

-



This article was previously published under Q289317





SYMPTOMS
You may be unable to use the Microsoft FrontPage Database Interface to edit records in a database that you created to store the results from a form created in FrontPage.

When you attempt to save edited records, you may receive the following error message:

Database Results Error

Description: [Microsoft][ODBC Microsoft Access Driver] Syntax error in UPDATE statement.

Number: -2147217900 (Ox80040E14)

Source: Microsoft OLE DB Provider for ODBC Drivers

You may also receive the following error message

One or more form fields were empty. You should provide default values for all form fields that are used in the query.

and the changes are not saved to the database.



CAUSE
This behavior can occur because databases created through the properties of forms in Microsoft FrontPage 2000 or Microsoft FrontPage 2002 cannot be used directly with the Database Interface Wizard in FrontPage 2002. The reason for this is that the Timestamp field, which is mandatory in such a database, is a SQL data-type and must be enclosed in brackets if used as a column name in a database query.



WORKAROUND
Microsoft provides programming examples for illustration only, without warranty either expressed or implied, including, but not limited to, the implied warranties of merchantability and/or fitness for a particular purpose. This article assumes that you are familiar with the programming language being demonstrated and the tools used to create and debug procedures. Microsoft support professionals can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific needs. If you have limited programming experience, you may want to contact a Microsoft Certified Partner or the Microsoft fee-based consulting line at (800) 936-5200. For more information about Microsoft Certified Partners, please visit the following Microsoft Web site:

https://partner.microsoft.com/global/30000104

For more information about the support options that are available and about how to contact Microsoft, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

To work around this issue, modify the page code produced by the Database Interface Wizard so that it works correctly. To do this, follow these steps:  Open the Web in FrontPage. In the Folder list, click the plus sign (+) next to  _interface, where  is the name of the database connection in FrontPage. Click the plus sign next to Results. Click the plus sign next to editor. Double-click update.asp, and then click the HTML tab.  Find the line beginning with the following <!--webbot bot=&quot;DatabaseRegionStart&quot; ... and in that line, find the following clause: Timestamp = '::Timestamp::' </li>  Edit that clause so that it reads as follows: [Timestamp] = '::Timestamp::' </li> Save the page.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

<div class="moreinformation_section">

MORE INFORMATION
This behavior occurs because the database created by FrontPage automatically includes a field named Timestamp, and you do not have the option to remove that field when the database is created. Timestamp is a reserved numeric type in SQL. Therefore, when the Update query in the Database Editor is run, an error message is generated.

The behavior described here arises within the operation of FrontPage, but you may encounter similar issues if you use databases that have been created by other means and that use reserved words as the names of columns in tables or in queries. It is best to avoid the use of reserved words entirely, but if that is impossible, the workaround described here (enclose the column name in the delimiters [ and ] ) may be helpful.

Additional query words: prb

Keywords: kbbug kberrmsg kbnofix KB289317

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.