Article ID: 314440 - View products that this article applies to.
This article was previously published under Q314440
In Microsoft Office FrontPage 2003 and in Microsoft FrontPage 2002, when you submit a form, a confirmation page appears. This gives you the impression that the form was submitted successfully, but no information is written to the database.
This problem occurs if you mark a field in the database as a primary key and then submit a form that duplicates data that was previously submitted in a field marked as the primary key field.
For additional information, see the "More Information" section later in this article.
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers 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 requirements. To work around this problem, follow these steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
When you define a field as a primary key in Microsoft Access, all records must have a unique entry in that field. If you attempt to enter duplicate data into the field, Access returns an error.
When using the FrontPage 2002 Server Extensions or the FrontPage 2000 Server Extensions, if you attempt to submit a form to a database with duplicate data in a field marked as a primary key, the following error message appears:
In FrontPage 2003 and in FrontPage 2002, the following line is added to the FP_DumpError function in the Fpdbform.inc file:
Cannot update the database.
This line of code is added to the file to improve cross-codepage support. It causes FrontPage to ignore the error that Access returns when a Web page attempts to add a record that contains duplicate primary key data, but it allows the confirmation page to be displayed. The operation appears successful, but Access does not allow the record that contains the duplicate primary key data to be written to the database.