The fix was to remove NOF, reinstall version 9, and reinstall update #2
(assuning you've still got it on your computer.) This allowed me to
continue working and await the repaired update 2.

Laurence

Jack wrote:

>I feel for you Laurence. This is discraceful stuff .
>
>Hopefully they will be professional enough to provide a quick solution to
>this (eg: a working update) to help you out.
>I also hope that your clients won't be too upset and that you have some
>recourse if it has affected you financially.
>
>
>"LBA" <webdesigns@no2spamabramsnet.com> wrote in message
>news:dt3ncb$ljm3@news01.netobjects.com...
>> Perhaps that is so, Chuck, but I just got myself into even deeper trouble.
>> I attempted a System Restore to revert back to the un-Updated version of
>> NOF 9... which it did... but then when I attempted to open my nod file,
>> NOF reported that the site was created with a newer version of NOF... the
>> updated version... and it refused to open the file. I am dead in the
>> water.
>>
>> Laurence
>>
>>
>>
>> Chuck «BeyondFusion» wrote:
>>
>>>Laurence,
>>>
>>>Actually, a form that currently has an action is not affected by the bug.
>>>It only affects new forms created in 5016.
>>>
>>>

>
>
>
>