Hi Orman,
This is a known issue in FrontPage 2003, Refer :
http://support.microsoft.com/?id=817029
Work around:
==========
The workaround is to manually update the s-columnnames and s-columntypes
values in the DatabaseRegionStart webbot code.
To do so, us the following steps:
1. Create a new ‘default’ Database Results Wizard page with the same table
as in the page giving the error.
2. Switch to HTML view.
3. Locate the following section of code:
<!--webbot bot="DatabaseRegionStart"
4. Copy the following text of s-columnname and s-columntype [example given
below].
s-columnnames="Expr1000,EmployeeID,FirstName" s-columntypes="3,3,202"
5. Open the page that is returning the error in FrontPage 2003.
6. Switch to the HTML view and locate the following section of code:
<!--webbot bot="DatabaseRegionStart"
7. Update the s-columnnames value to include all field names, including
derived
names for fields from aggregate functions like COUNT, etc. For example:
s-columnnames="Expr1000,EmployeeID,FirstName"
8. Update the s-columntypes value to include all field types, including
derived
types from aggregate functions like COUNT, etc. For example:
s-columntypes="3,3,202"
Regards,
Vijay
Disclaimer: This posting is provided "as is" with no warranties and confers
no rights
--------------------
| From: "Orman" <
[email protected]>
| Subject: database results page
| Date: Thu, 11 Mar 2004 22:18:04 -0500
|
| Since we upgraded to Front Page 2003, the dynamic link between Front Page
| and MS ACCESS became very unstable. The form based queries and updates of
| ACCESS database tables are giving a variety of error messages. It became
| case sensitive. It gives error messages if the forms or asp pages are not
in
| the root web. And a variety of other errors that never existed in Front
Page
| 2002. What are we doing wrong?
|
|
|
