Frontpage 2003 Database Results - Insert parameter - How ?

[Guest]

EARLIER VERSIONS OF FRONTPAGE
=======================
With previous versions of frontpage it was possible to call a page and pass
parameters :-
i.e.
index.asp?rtype=A

You could then use this variable to query database results
i.e.
select * from mytable where recordtype = '::rtype::'

FRONTPAGE 2003
============
As soon as frontpage 2003 is installed, these "parameters" cease to work and
the following error appears
"Database Results Wizard Error
Your page contains a query with user input parameters that could not be
resolved.
This could happen if your DatabaseRegionStart webbot has an empty or missing
s-columnnames or s-columntypes attributes.
You may need to read Microsoft Knowledge Base Article 817029."

There must be a simple way of using parameters in frontpage 2003 but all I
can find through the search engines are hundreds of people with the same
problem

There does seem to be a workaround by copying
_FPClass\fpdblib.inc
_FPClass\fpdbrgn1.inc
_FPClass\fpdbrgn2.inc

from an old website (running frontpage 2002 or earlier) but surely this
can't be correct, otherwise why would new "modified" versions of these files
be installed in Frontpage 2003 ?

Anyone any idea's of a real fix ?

 

[Ronx]

The workaround is the easiest fix.
The only alternative is to start again with new pages, and do NOT
copy anything (especially the webbot code) from the old page to the
new. The new pages can use the DRW or DIW, or be custom written.
The code written by FP2002 SP2 and earlier is not compatible with the
new versions of those files. FP2002 SP3 gives the same problem as
FP2003.

The new versions of the files fix a security problem that exists in
the old, so changing to the old version implies a security risk

 

[Guest]

Thank you for taking the time to post the entry.
I removed Frontpage 2003 and IIS from my PC (and removed c:\inetpub and all
of its contents) and reinstalled Frontpage and IIS.

I then created a new file index.asp and created database results on it.
All fine until I inserted a parameter again and then the same problem
occurred which I find very strange.

Was hoping that recreating a new page would resolve the problem but it
doesn't seem to have.

Any other ideas?

 

[Ronx]

No other ideas. I used the new page method, without uninstalling
anything, and never had a problem. My DBRs are "fed" from forms using
POST and by parameters in hyperlinks, though I am converting my pages
to custom written ASP.

 

[Guest]

Hi Ron
I reinstalled / cleared IIS again and it seems to be working now. Spend most
of the day recreating my site but its all up and running now.

I did notice that Frontpage now seems to be case sensitive on "fieldnames".
All up and running again! Roll on Frontpage 2004 S

Thanks again for your help
Simon