Datasheet

RAIS 3.0 Programmer’s Guide – Part I : Advanced Customization
47
[RAN - ]
[Calculation - ]
[Export Selection - ]
[Exportable Selection - ]
[Exported Selection - ]
[Exported Overall Selection - ]
[Import Selection - ]
[Importable Selection - ]
[Imported Selection - ]
[Imported Overall Selection - ]
[Menu Selection – ]
3.1.2 Complex, multiple selection managing queries
Allocation and un-allocation queries are required for managing multiple selection fields.
These SQL statements are generated only during the creation process of the RAIS User
Interface. Only simple default definition of allocation and un-allocation queries are
generated, which might not necessarily always fit the demands. Hence, developers have been
granted the possibility to overload automatically generated allocation and un-allocation
queries by predefining them inside the RAIS Creator. The RAIS Creator will generate only
those allocation and un-allocation queries that have not yet been defined inside the creator. If
queries already exist, the Creator will simply copy them into the Front-End.
Prefix
[Allocation - ]
[UnAllocation - ]
3.1.3 Completing the integration of the new queries in RAIS
In order for the new queries that have a prefix different from the two lists above (for example
"CUSTOM - ") to be created upon next run of the creator, it is necessary to modify the
creator source code as described below:
Open RAIS 3.0 Creator in design mode
Locate the function [Public Function CreateQueries] in the module [RAIS Database
Creator Functions]
Include a line CreateQueriesRange db, "CUSTOM - "
3.2 Copying forms and reports
Forms are most easily copied by a simple Drag-and-Drop operation from the Front-End into
the Creator. If the form to be copied already exists in the Creator, MS Access will ask for a