| Home | Getting Started | Using the Template | Task Guides |
Searching and tagging are only the beginning. xSearch lets a user select records in an ABC Browse and then use that selection when printing a report or running a process. You do not have to recreate the same selection in a second window.
Important: A report is not automatically filtered just because its key or file matches the browse. It needs the xSearch report extension and compatible tag storage configured. The calling button merely starts the report; it need not be located on the tagging browse.
Use xSearch 5.0 for Process on a Clarion process procedure. Configure the same tag storage and unique field, then choose the prompt and no-tags behavior on its Question tab. When the process is run, xSearch can skip records that are not tagged while retaining the process’s existing selection and sorting rules. Its progress indicator counts records read, not just the tagged records processed.
xSearch 5.0 also includes a dedicated xSearch 5.0 for Fomin Report Builder procedure extension. Add it to a Fomin RunTimeReport procedure, match the tagged browse’s External File, This File, or Global Queue storage settings and unique field, and configure the same Question choices used by the standard report extension. When tagged-only printing is selected, it skips untagged records during the Fomin runtime report’s normal record traversal.
This extension is intended specifically for Fomin Report Builder RunTimeReport procedures. It does not make every Fomin report tagged-only automatically, and the separate Fomin product must be installed to create those procedures. The calling button can remain an ordinary Call a Procedure button.
See Procedure Extensions for all five xSearch procedure extensions and the difference between developer-added report/process extensions and imported-window support extensions.
The Browse Local Queue exists only inside that browse procedure and cannot serve as a shared selection for an independent report or process. To reuse tags between procedures, select an appropriate shared method such as Global Queue (until the application exits), External File (across sessions), or This File (tag field in the actual record), and configure matching definitions. The report/process extension supports the applicable External File, This File, and Global Queue options.
For multi-DLL applications, put shared declarations and matching settings in the participating APPs. A report may live in a separate Reports DLL and be called from the main EXE; avoid introducing circular DLL dependencies. See Multi-DLL Setup and Choose Where Tags Are Stored.
The Question tab controls whether to ask about tagged records, whether to show the count, and whether a no-tags run should process everything, nothing, or ask anyway. These are configurable choices, not an unconditional promise that every report is tagged-only.
See Search and Tag Controls for the browse buttons, and Export Records to create data files from tagged records.
| Home | Getting Started | Using the Template | Task Guides |