db Editor Fails in FP2003

[samG]

Running FP2003 and Access 2000. Everything works fine except for the
Database Editor. When submitting the edited record, the following error
response shows:
"DATABASE Results Wizard Error. The operation failed. If this continues,
please contact your server administrator." I have read 2 separate problem
posts regarding a similar issue. The responses were not too encouraging.
Yes, I reviewed the KB articles that everyone of the replies had, plus I have
just finished with MS's site and looked at KB891819 and KB817029. I run 2
Access db's in 1 site, so I tried KB891819 on the section were the least
amount of damage might happen to my layouts. Using method 1, which makes no
sense to do, I did and just what I thought would happen, the layout went back
to the original form, but what ticks me off is the damn thing still did not
edit, but failed as before. It appears I will have to return to FP2000 where
I have successfully had Access db websites that ran without a flaw. Any
Comments ?

 

[Stefan B Rusynko]

While testing turn on fg debug to see more meaningful error messages from the DBRW
To see the true error, open the hidden folder /_fpclass/ and edit the fpdbrgn1.inc file
At about line 19, change : fp_DEBUG = False to : fp_DEBUG = True
- post back w/ the real error

KB 891819 only applies if you have tables w/ spaces in their table names
(use method 2 as you should not use tables or fields w/ spaces in their names)





| Running FP2003 and Access 2000. Everything works fine except for the
| Database Editor. When submitting the edited record, the following error
| response shows:
| "DATABASE Results Wizard Error. The operation failed. If this continues,
| please contact your server administrator." I have read 2 separate problem
| posts regarding a similar issue. The responses were not too encouraging.
| Yes, I reviewed the KB articles that everyone of the replies had, plus I have
| just finished with MS's site and looked at KB891819 and KB817029. I run 2
| Access db's in 1 site, so I tried KB891819 on the section were the least
| amount of damage might happen to my layouts. Using method 1, which makes no
| sense to do, I did and just what I thought would happen, the layout went back
| to the original form, but what ticks me off is the damn thing still did not
| edit, but failed as before. It appears I will have to return to FP2000 where
| I have successfully had Access db websites that ran without a flaw. Any
| Comments ?
| --
| samG

 

[samG]

Thanks for trying to help Stefan, but I have pulled the website and going to
do it in FP2002 where I have several FrontPage websites running with Access
2000 without a flaw for at least 2 years. I am just pissed at the time I
have spent doing this new website in FP2003. By the way, I did try doing
some of what you said, but nothing helped. Now, off to rebuilding this new
website. Later