We upgraded one of our client’s servers to 6.5.1 the other day, all seems to work reasonably well except for the $search form which does not seem to search. It uses fields to build up the query in the $$Return field, and then uses SearchView on the same database to bring up the search results (using the square bracket notation ). It does use values from Computed for display fields (especially for the location of the database), however using a hard-coded URL ([http://www.lotus.com]) also does not run. There is no error and no entry in the log, simply a Form Processed message on the screen, as if it hasn’t noticed that the $$Return field (which is hidden from web and notes) is there. There is also a “$$SearchTemplate for viewalias” form which shows the results. If I type the URL directly into the address bar it works correctly…
I did have a problem with the subform being hidden from the form in designer because of the “Hide from Notes” being displayed, an issue which I believe was new with 6, and this has now been rectified. Any ideas? I’ve had a good search but haven’t come up with anything yet (lets hope the criteria I’ve searched for is right…) - any help would be greatly appreciated.
After much testing the problem appears to be that the subform is still not being recognised after the submit (an HTML submit button) - therefore the $$Return (which is on the subform) does not run, and trying to access the subform fields in the WebQuerySave of the form events just returns empty values.When I remove the subform from the form and copy and paste the subform fields into it instead, all works. A new (major - especially for existing apps) bug or am I being stupid? Maybe something has changed from previous versions that I am unaware of…
I’m running into similar problems with using subforms. I’ve discovered that @DbName does not perform the same in a subform as it does if it is on the form. When submitting a form the $$Return loses the value of @DbName if it is retrieved from a subform.
I also had this problem, and it turned out to be because subforms dont inherit the “available to public access users” setting of the form they are imbedded in. If your search form is accessed via the “available to public access users” setting (as opposed, for example, to allowing anonymous users editor access to your DB), you also need to allow public access users to access your subforms (check the box in the security tab of the subform properties dialog).
Thank you, that solved my problems, I have a custom searchform with several subforms for my website, and they failed to show up when displaying the results. This solved it!