>> The only way to fix this is to either recreate the browse procedure from scratch or to copy the browse and use a new procedure name for the copy. The copy will then work fine - but then a month or a year later, the same problem returns - I cannot see what I may be doing to cause this - really no rhyme or reason.
In any case where you have a "have to rebuild procedure from scratch to fix problem" it's useful to save the generated CLW before the re-creation, and again after the recreation. Obviously the source code is different, and from that one can usually determine what setting is different.
In this case I suspect the data, not the procedure itself. Recreating it is likely just changing the default sort order or something.
If you click on a button, and it does nothing, then check the FireBug console to see if there is an error in the returned xHtml.
Typically it's the data that's the root of the problem, not the procedure.
cheers
Bruce