Datasheet

RAIS 3.0 Programmer’s Guide – Part I : Advanced Customization

Another way to test is by means of queries. Create a new query, having the following SQL

statement

SELECT RAIS_IV("regulatory authority number") AS Expr1;

Run this query in datasheet view, and you will see that again the new authority number is

displayed. Later sections in this document will make use of especially this functionality.

2.7.2 Comments

When implementing new functions or procedures, we should take care not to introduce

naming conflicts. Such conflicts will arise when a function, procedure or variable is defined

twice. To avoid duplicates and overwrites, it is highly recommended to use the prefix

“CUSTOM_” for all your custom function definitions; this prefix is not used by IAEA RAIS

Developers in any code part. In addition, we recommend saving all custom definition in

custom code modules. All custom code modules should again have the prefix “CUSTOM – “

(RAIS developers will not use this prefix).

Helper functions, as implemented in example 2, shall only be used in early development

phases of new queries. Please keep in mind that future development of RAIS will point into

the direction of SQL Servers. Helper functions will then degrade performance of execution

times of queries, as these helper functions will be executed locally.

Functions and procedures are stored in modules (stand alone modules or form modules)

within Microsoft Access. To avoid for loss or overwriting of custom functions and

procedures, it is highly recommended to store them in separate stand alone modules.

Note:

Avoid defining global variables, side effects are inherent.

Define local variables as well as sub level functions and procedures to be private.

Avoid using DLL functions directly by using Declare statements, CreateObject is to be

preferred for compatibility to future releases of Microsoft Office.

2.8 Creating Custom Forms

The best approach for creating new custom forms is:

• Create and design the new custom form in an unlocked front-end

• Test, debug and validate the new custom form

• Copy the final new custom form in the RAIS 3.0 Creator (hereafter referred to as

[source form])

The next step is to make your new custom form accessible via the treeview menu

• Create the record entries to bind the new form to a new menu point (see section 2.10)

Modify the RAIS 3.0 Creator for the new custom form to be created upon the next creation

run. See section 3.2 for details