C
Chris Freeman
As usual, I haven't lenred my lesson to not upgrade, and
I did to Frontpage 2003. I create Access driven page ,
and use the criteria function to creat filtering pages by
coding: fp_sQry="SELECT * FROM Projects WHERE (Proj_ID
= ':
roj_::')"
In FP2002 everything ran fine, until I upgraded to
fP2003. Now I get a "Database Results Wizard Error
The operation failed. If this continues, please contact
your server administrator."
I thought maybe something in the syntax changed, but the
same thing happens when I use Microsoft to code it as
well. But if I don't use a variable, and predetermine
tohe filter by using Proj_ID = '1015', it works fine.
Someone told me to change the fpdbrgn1.inc fpdebug
status to True, but the problem persist. And as usual, it
has screwed p everyhting and I can't uninstall to get rid
of the problem.
Does anyone have any ideas?
Thanks for trying
Chris
I did to Frontpage 2003. I create Access driven page ,
and use the criteria function to creat filtering pages by
coding: fp_sQry="SELECT * FROM Projects WHERE (Proj_ID
= ':
roj_::')"In FP2002 everything ran fine, until I upgraded to
fP2003. Now I get a "Database Results Wizard Error
The operation failed. If this continues, please contact
your server administrator."
I thought maybe something in the syntax changed, but the
same thing happens when I use Microsoft to code it as
well. But if I don't use a variable, and predetermine
tohe filter by using Proj_ID = '1015', it works fine.
Someone told me to change the fpdbrgn1.inc fpdebug
status to True, but the problem persist. And as usual, it
has screwed p everyhting and I can't uninstall to get rid
of the problem.
Does anyone have any ideas?
Thanks for trying
Chris