Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

This article was previously published under Q289317

↑ Back to the top


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.

↑ Back to the top


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.

↑ Back to the top


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 Microsoft Advisory Services. For more information, visit these Microsoft Web sites:

Microsoft Certified Partners - https://partner.microsoft.com/global/30000104

Microsoft Advisory Services - http://support.microsoft.com/gp/advisoryservice

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:
  1. Open the Web in FrontPage.
  2. In the Folder list, click the plus sign (+) next to myConnection_interface, where myConnection is the name of the database connection in FrontPage.
  3. Click the plus sign next to Results.
  4. Click the plus sign next to editor.
  5. Double-click update.asp, and then click the HTML tab.
  6. Find the line beginning with the following
    <!--webbot bot="DatabaseRegionStart" ...
    					
    and in that line, find the following clause:
    Timestamp = '::Timestamp::'
    					
  7. Edit that clause so that it reads as follows:
    [Timestamp] = '::Timestamp::'
    					
  8. Save the page.

↑ Back to the top


Status

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

↑ Back to the top


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.

↑ Back to the top


Keywords: KB289317, kbnofix, kberrmsg, kbbug

↑ Back to the top

Article Info
Article ID : 289317
Revision : 6
Created on : 1/31/2007
Published on : 1/31/2007
Exists online : False
Views : 267