REM  *****  BASIC  *****
REM This module contains variables, which are used very often by many of the following macros.
REM Variables, wchich are declared here, mustn't be declared ad the beginning of every procedure.
REM It could be, that variables, which are declared outside a procedure, contain a value when you change from on procedure to another.


REM Variables to get access to the database
DIM oDataSource AS OBJECT	' This is the used data source. If a second datasource should be used, it must be saved in another variable.
DIM oConnection AS OBJECT	' Only one connection to the database is necessary to use for queries, updates, deletes and inserts.
REM The following three variables are used to create and execute a SQL-command.
DIM oSQL_Command AS OBJECT	
DIM stSql AS STRING
DIM oResult AS OBJECT
REM If there are more than one SQL-commands running, there must be added more variables. 
REM The following two variables are used to execute another update, insert or delete.
REM If you wish to execute a query there must be another variable for the content given back from the database.
DIM oSQL_Command1 AS OBJECT	
DIM stSql1 AS STRING

REM Variables to get access to forms
DIM oDoc AS OBJECT	' Access to the database document - all the following procedures were running in the same document. So it could declared at the beginning.
DIM oDrawpage AS OBJECT	' Access to the drawpage, in this case the form	- could be declared at the beginning, because all procedures refer to only one form.
DIM oDocCrl AS OBJECT	' Access to the controller of every field of a form

REM It's difficult to get all methods, properties or services of a field of a form. If you use dbg_methods and so on, you could get too much informations.
REM The whole informations couldn't be shown on the screen by msgbox.
REM This is the included tool of LO to see all methos and so on of one field:
REM		GlobalScope.BasicLibraries.LoadLibrary("Tools")
REM		WriteDbgInfo("fieldname")
REM It is created a writer-file, which could fill more than 5 pages.

DIM oDlg AS OBJECT 'The dialog must be started from one procedure and uses also other procedures. So it must be a varibale of the type "public"