Fix for Windows Server 2003 / FrontPage Database Query Errors?

[Myron Johnson]

Like a lot of folks, I'm getting errors on all database queries
written by Frontpage.

I had a totally functional website, orginally created with FrontPage
2002.
This site works fine on my Windows XP Professional-hosted sites with
FrontPage 2002 Extensions enabled. My databases are all MS Access
2002.

Now, I've set up a Windows Small Business Server 2003 site. After
publishing to the site, all the pages that have FrontPage-created
database queries give the following error:
==========================
Database Results Error
Description: Syntax error in query. Incomplete query clause.
Number: -2147217900 (0x80040E14)
Source: Microsoft JET Database Engine
==========================

I tried updating to FrontPage 2003 and erasing and then re-creating
the queries. Same results. FrontPage 2002 extensions are enabled.

Searching deeper, I've discovered that FrontPage-created queries that
do NOT contain Access Queries (for example, those that list ALL
records in a table) will display properly. But any Access-created
queries give the error above. I then updated to MS Access 2003, but
the problem remains.

My pages using hand-written database queries seem to be OK, but I
really hate to re-write a whole bunch of pages, eliminating all the
FrontPage-created queries.

Anybody solved this problem yet?

 

[John Jansen \(MSFT\)]

This is probably an issue that I am currently trying to nail down. Your
error is a bit different, but try this first:

When the custom query is done on the update page that sends the change to
the database, it doesn't seem to include the field names and attributes in
the database region of the page. On the update page, look for "<!--webbot
bot="DatabaseRegionStart" s-columnnames s-columntypes" in the code view of
the update page and add the names of the two fields referenced in the query
and the appropriate code for the type of field it is. For example:

s-columnnames="FOO,BAR" s-columntypes="202,202"

I have two fields here, and both are set up as text fields in the DB (202.)
Other codes are 3 for numeric, 135 for dates, 203 for memo (I think.) So if
I decide to use a numeric field for price, it should be:

s-columnnames="FOO,BAR" s-columntypes="202,3"

Please let me know if this helps.

 

[Myron Johnson]

Like a lot of folks, I'm getting errors on all database queries
written by Frontpage.

I had a totally functional website, orginally created with FrontPage
2002.
This site works fine on my Windows XP Professional-hosted sites with
FrontPage 2002 Extensions enabled. My databases are all MS Access
2002.

Now, I've set up a Windows Small Business Server 2003 site. After
publishing to the site, all the pages that have FrontPage-created
database queries give the following error:
==========================
Database Results Error
Description: Syntax error in query. Incomplete query clause.
Number: -2147217900 (0x80040E14)
Source: Microsoft JET Database Engine
==========================

I found MY solution to this problem.

After considerable head-scratching, I found that if I used an Access
Query within the FrontPage Data Results Wizard (DRW), it won't work.

HOWEVER, in the FrontPage DRW, if I select a "Custom Query", and
insert the SAME Access Query, everything works fine. There is a
problem with what FrontPage is trying to do. The first time you open
the "Custom Query" dialog, you can see that FrontPage is putting
quotes (") around the Access query name. This won't work. But if you
replace the quotes (" ")) with brackets ([ ]), FrontPage DRW now
works!

Example:
What FrontPage tries to do: SELECT * FROM "My Query"
What is needed to work : SELECT * from [My Query]

I don't know why FrontPage is messing up the queries, but the "messed
up" queries work with IIS 5.0. But they don't work with IIS 6.0!