Cataloging of Programs compared to Direct Run
Preferred method now is "PixieEngine.ini", but you can also use tables/files named "md"
To call catalogued programs, scripts or ActiveX, simply enter the verb, which is the itemid of the catalog entry in file/table "md".  Using Microsoft Access to look at file/table "md" within account/database "testpxe1", 1st 4 attributes only shown:

A0	A1	A2	A3	A4
test1	ACTIVEX			px1.bp test1
test2	ACTIVEX			px1.bp test2
disptest	ACTIVEX			px1.bp disptest
pxu1000	ACTIVEX			px1.bp pxu1000
umenu	ACTIVEX			px1.bp umenu
stest1	VBSCRIPT			script1\stest1.txt stest1

• All values are case-insensitive. eg "vbscipt", "VBScript" and "VBSCRIPT" are all OK
• A0, the itemid, is the catalogued verb
• A1 is the nature of the program's run environment, ACTIVEX is for compiled .dlls from any language. 
  For a script, A1 needs to be the scripting language eg VBSCRIPT, JSCRIPT or PERL
• A4 is the program provider, then a space followed by the internal name of the sub or function to call. 
  In most cases, that internal routine name can be left out if it is the same as A0.
  For ActiveX the "provider" is the registered classname, which is usually project name, dot, internal class name.
  For Scripts, the "provider" is the file in the windows file system.  File paths can be relative or absolute.  In the above example, script1 is taken to be a subfolder off whatever folder contains PixieEngine.dll.
  Absolute paths could look like this:
  c:\progra~1\pixieengine\script1\stest1.txt stest1
  Note that because the file pathname "program files" has a space in it, it needs to be expressed as its alternative no-space version "progra~1".

Results of Queries, eg Select
Preferred method now is "SelectResult" but you can also use "SelectArray".
PixieEngine can represent query results internally as 2D arrays.  This gives a common presentation to results from differing datastores.  "SelectArray", the "old way", provides you with a local copy of this array rather than the faster "pointer reference" which was our original intention.  This array can be rather large and hungry on time and resources to copy, and we have also found it fails with scripting.  We would comment that we found the Microsoft documentation on this subject all too easy to misunderstand, and Microsoft technologies in general seem to have some problems with passing arrays as function arguments.

So, SelectResult takes the simpler, safer approach of reading individual elements out of PixieEngine as function calls while the true array remains as an internal entity.
Note that SelectResult may look like SelectArry with its identical syntax of "SelectResult(column, row), but it is an indirect "property of an array" rather than a full array in its own right.  That means that the UBound function can not be used with it, so we have provided an indirect equivalent to UBound to partner SelectResult:
nMaxColumnNumber = SelectUbound(1)
nMaxRowNumber = SelectUbound(2)