|
Create |
  
|
|
Create |
|
Click on "New" in the FRAME toolbar when this module is open to create a new connection.
A wizard will walk you though the necessary steps.
A first message will show up to let you define the ODBC Type of connection you want to create : DSN - HyperFile or SQL's (or Access or Excel)
DSN or HyperFile
If you select DSN HyperFile, a checkbox will be displayed to let you define if you will be using an existing System DSN to connect to the tables
If you define that you will use an existing DSN, you will be then be shown a list to choose from the system DSN's the one to use for this connection.
If you had defined that the DSN did not yet exist, DMC will open up for you the ODBC Manager and let you create it there - it will then open up the above mentioned screen with the same List for you to choose from ....
HyperFile
For any HyperFile ODBC connection the NAME MUST CONTAIN HF_ or hf_ for DMC to "see" it as such
Nothing has to be done - you can use the "Test" button
SQL or Access or Excel
Depending on your selections you will be then taken to the ODBC connection pre filled form for you to complete and Save.
SQL's
You have all the main items pre filled for you and just have to finish entering the proper data to build the connection string
Enter the required values (press "Tab" between each field)
SERVER NAME (if applicable) and press "Tab"
USERNAME to be used and press "Tab" (or in Ms SQL case check "Empty login if you want to create a Trusted Connection string)
PASSWORD to be used and press "Tab" (or again in Ms SQL case use the "Empty Pwd" checkbox to create a Trusted Connection)
DATABASE NAME and press "Tab"
You can also enter the PORT if required by your settings
Depending on the SQL type you will need or not to select the driver to use by clicking on the 'Select" button :
SQL Anywhere - Oracle - PostGreSQL - MsSQL and MySQL and Access and Excel :
You will also have to enter the Name of the Driver to use (example "Oracle in XE") - DO NOT USE the Microsoft one : it is too slow and it REQUIRES the Oracle one to be installed and used
You will NOT need to fill in the Server field with this driver (so it is hidden)
A button 'Select' is here for you to choose from the list of all ODBC drivers installed on your machine the one to use.
Access or Excel : you only need to select the MDB or XLS/XLSX file to use
For Postgre SQL you have to use the UNICODE version of the ODBC driver (and not the ANSI one which will not allow proper connections)
The Driver List is displayed for you to select with a simple Double-Click on the appropriate driver
You can also of course change the selected driver from this list at any time when editing the record
DB2 : You have to use the ALIAS of the Table name
You can modify any field if need be and after again pressing "TAB" the entered value will show in the connection string ....
Do not forget to fill in the TEXT and IMAGE fields with LENGTH values (BLOB's and IMAGE's) - by default the tool will fill in 512 if you forget so as not to block your imports(MEMO and BLOB fields not seen).
You can define EMPTY passwords if you need to by using the appropriate checkbox :
When the connection string is filled in with the DSN name on your machine (and other checkbox's filled with Worksheet if need be) then you can use the "Test ODBC" button and if all is fine you will see all Access Tables or all Excel Sheets.
You also have the name of the server connected to for better information....
* TIP & TRICK :
some older versions of some SQL's can give you problems to connect or when reading - transferring data
You can use this "trick" to test and use DMC in "limited" ways (no sql specific features and functions like GUID or server side defaults etc)
Create a SYSTEM DSN pointing to your SQL DB and use (and create in DMC) a DSN "type" of connection
Some users for example requiring to connect to version 6 of SQL anywhere could not get the proper settings (keys etc read) when using an SQL connector
The system tables DMC uses to query the server did not exist in those older versions and the KEYS were not properly returned resulting in errors while reading tables
Creating a DSN "type" of connection solved this issue.