Skip to main content
September 10, 2008
Question

Update Record Problem

  • September 10, 2008
  • 1 reply
  • 224 views
Hello

I have a problem with the update record behavior on an ASP web page. It has red
exclamation Mark next to it when I create the recrdset. I have a filtered record set, and it is being displayed in a repeated region, every time i try to open my update record behavior, i get the
following error. "The original recordset specified in this script was not found."


I have removed the recordset and re-created it many times but the issue remains
the same.

I have even re-installed MX2004 in case there is an issue with that, but no joy there either.

I would appreciate any help with this that I can get!

Steve
This topic has been closed for replies.

1 reply

Inspiring
September 12, 2008
I have had this no end of times with MX and it didn't really have any major effect on my files. I still get it with pages created in MX when I open them in my CS3. I often just used to restart DW and it would go away.

However, you could go to your code view and locate the recordset sql, copy it, create a new recordset, then either paste the sql in the advanced window, or just create a SELECT * FROM blah blah, click OK and then find the new recordset sql code (in code view) and paste the old sql code in place of the new. Then delete the old recordset and probably best while in the code view rather than the server behaviours panel as this panel might remove any dynamic content related to the old recordset.

Of course doing this has knockon effects with everything dynamic on your page, so you will need to do a find/change so that any content referring to your old recordset is update to the new.

If that don't work, save a copy of your page, strip all dynamic related content out and start again.

These are painful methods sometimes, but they often resolved my problem.
September 16, 2008
Thanks for your response...good to know I'm not alone!...I think there is something fundamentally wrong with my approach to manipulating data, but really needed to know that DW is functioning correctly in order to move on...cheers

Steve