ExecDQL

Function::Internal

ExecDQL
ExecDQL("DQL Script","Data-Entry Field1","Data-Entry Field2","Data-Entry Field3","Data-Entry Field3","Export File")
ExecDQL("delete records in MyTable.")
ExecDQL("for My Table with MyField=Data-Entry Field1 ; modify records My Field2=data-entry field2 .",

To run a DQL script as a function from anywhere.

DQL is the most useful part of a DE application but it has had its limitations because it has been part of the DQL document (report). With ExecDQL we have liberated it, and you can now call a DQL from anywhere at anytime. It follow normal DQL syntax rules and it will generate an variable length export file if you include a file name as the last parameter (parameter 6).

Because it is a function you have to reference the Data-entry fields (transfered as parameter 2-5) with fixed names i.e Field1, Field2, Field3 and Field4. Other than that it is completely traditional DQL.

The ExecDQL has the GUI context of the document from where it is called, so you can read and manipulate the document from the DQL. This means that ExecDQL is not only a Data manipulating procedure it can also be a GUI manipulating procedure.

If you need more input variables than 4 you can simply pick them out of the Form you are calling the ExecDQL from with GetValue()

To make ExecDQL and other parts of DE8 more effective we have also introduced ESCAPE values in DE8 Strings.

Early in 8.0 we introduced CHR() to make it easier (possible) to use reserved letters in DE derivations and DQL etc. However it is a little awkward when you have to use ConCat() to joint things together for instance in a ExecDQL etc.

Ex.
ExecDQL(concat("message ", chr(34), "Hello world!",chr(34)," window.","","","","","")

So now you can simply do this with the escape charcter for ".
Ex.
ExecDQL("Message /'Hello World!/' window .")

The observant reader also see that we don't add all the "" at the end of the function. This is news in 8.2 too. We have introduced variable number of parameters to make the functions more user friendly.

Up to now you had to be exact with your parameters and that could be a chore when the only thing you wanted was to execute a small line of commands with no export, and no input.

You will still have to follow the numbers so if you want to include an export file for ExecDQL you will need to include 4 empty "" as parameters before the export file name, but if you only need two data-entry parameters you can now simply add the two and skip the 3 last parameters.

Parameters

DQL: (String)

Here you can write a DQL direct into the execdql. The length of the dql follow the same rules as any string added to input. It will be auto escaped if you not use any of the spesial formatting It can do anything a DQL can do and has the same format as any other DQL You can also add a field name read the information from a text or memo field. If you add raw: in the start of the text it will not be auto escaped. Iff you add file:filename it will read the dql from disk. If you add lable:lablename it will read it from a label. If you add @dqlname it will read the dql from $$DQLStore$$ table using DQLName field to lookup the script. If you use #number it will use DQLId to look up a numbered dql. The DQL will be stored in DQLScript field in the table. Same rules applied to Body execpt that is read from DQLBody field.

Data-Entry Field1: (String)

This is the parameter that you can reference inside the DQL script as Data-Entry field1.

Data-Entry Field2: (String)

This is the parameter that you can reference inside the DQL script as Data-Entry field2.

Data-Entry Field3: (String)

This is the parameter that you can reference inside the DQL script as Data-Entry field3.

Data-Entry Field4: (String)

This is the parameter that you can reference inside the DQL script as Data-Entry field4.

Export File: (String)

Body:

Here you can add a body format to generate output from the dql. It can take all the same input types as the DQL

ExecDQL was designed to cover two major flaws in the DQL hierarchy of DFW. Manipulation and export so if you add a file name her and a list records in the DQL it will create a CSV file with column headers where the columns are in the order you put them in the list records.

PS! It is extremely quick.

Returns/Result

Nothing

The setting for execdql @name and #id

All of this has to be set in the [EXECDQL] section unless used in server as you can have one for each prefix set and set it direct into this section instead.