Working with Local File to DB Process
Process Purpose
The Local File to DB process is used to import data (insert records) from a data file into a database table located in a specific Host server.
The remote database profile you create within MCL-Designer V4 is responsible for the direct communication between your MCL-Designer project and a remote database.
Once the project is loaded into a device, that same profile can be used to allow communication between the device and the remote database/host server, via MCL-Net. Therefore, make sure that the connection string of the selected profile includes an OLE DB provider that is compatible with the intended remote database. Ex: If you intend to use an Oracle database, select a remote database profile with the corresponding Oracle OleDB driver.
When you add a process, you are required to define its settings. This occurs in the process's properties window which is displayed automatically after having added the Local File to DB process. The properties window includes two tabs - "General" and "Advanced".
If any subsequent edition is required, double-click the process to open its properties window and enter the necessary modifications.
General tab
Fill in the following options:
Host Name & Data Source |
|
Host Name |
Select a host profile from the drop-down list or click See To Create a Host Profile or To Edit a Host Profile or The <Default> Host Profile. |
Data Source |
Select the database for the import from the drop-down list or click |
Insert into ‘table’ (DB Fields…) values (…) |
|
Table Name |
Select the table that will receive the imported records from the drop-down list. |
Local File Name |
Select the source data file that contains the records to import from the drop-down list. If needed, click |
DB Field Name column |
Select the field(s) that will receive the imported records from the drop-down list. |
Value/Variable column |
Select the data file value or click |
Example
The selected import destination is the "Inventory" database, more specifically, the "Items" table (the "ItemNumber" and "ItemDescription" table fields). The imported data ("<Product>" and "<Description>")come from the local file "<Inv>". |
Use the editing icons to the right of the table to move the rows up and down and to delete or add more rows.
Go to the "Advanced" tab.
Advanced tab
If … Go to |
|
DB Error |
Select a target location from the drop-down list or the |
Comm Error |
Select a target location from the drop-down list or the |
SQL request name (Must be unique) |
|
Name |
Define a unique name for the SQL request. One is always suggested. |
Detail of window:
"S:Menu" is a screen included in the same program as the process.
"R:Routine_1" is a routine included in the same program as the process.
If required, use the following recurring icons on the properties window:
Used to setup a time out. See Time Out.
Used to create a new data file. See Creating a Data File.
Used to edit a Data File. See Editing a Data File.
Used to test SQL Scripts. See To Test SQL Scripts
Use the icon to attach any relevant notes to this process. Click it and enter your notes in the resulting text box. These notes will be displayed in the corresponding "Actions" tab or "Process" window (in the "Notes" field) and in the "Developer Report".
After filling in the required options, click to conclude or
to abort the operation.
The added process is displayed in the corresponding "Actions" tab or "Process" window.
You can use relative paths to refer the file(s) you want to use in your project. See Working with Aliases.
Use the right click in MCL-Designer's input boxes to access certain features regarding the input box's option as well as general actions such as "Copy"; "Paste"; "Search".
Ex: If you right-click the "Variable" input box (included in a "Conversion's" properties window), you are provided with the "Search..."and "Variable Select" options.
If you right-click another input box, it will provide other possibilities.