Movicon Help on Line - Rel. 11.7.1301
ODBC connections are created by using plugins found in the "ODBCMgr" folder. Movicon installs some predefined plugins but other customized ones can be added in order to be used with different databases.
The meanings of the different parameters which must be configured using the "for the different plugins are briefly described below and are configured using the "Customize ODBC Settings" or "ODBC Settings" command for the different plugins.
Driver: this is the ODBC driver used by Movicon for connecting to the database. Default value: "Microsoft Access Driver (*.mdb)" (driver preinstalled by Movicon).
Database: this is the name of the .mdb database which will be created in the project's "DLOGGERS" subfolder and which the created ODBC connections is referred to. If this field is left empty, the database's name will be the same as the project's name.
MS SQL Server 2000, 2005, 2005 Express, 2008 and 2008 Express, 2012 and 2012 Express, 2014 and 2014 Express, 2016 and 2016 Express
Driver: this is the ODBC driver used by Movicon for connecting with the database. The default values are:
MS SQL Server 2000->"SQL Server"
MS SQL Server 2005->"SQL Native Client"
MS SQL Server 2008 and 2008 Express->"SQL Server Native Client 10.0"
MS SQL Server 2012 e 2012 Express->"SQL Server Native Client 11.0"
MS SQL Server 2014 e 2014 Express->"SQL Server Native Client 11.0"
MS SQL Server 2016 e 2016 Express->"SQL Server Native Client 11.0"
Server: this is the name of the SQL Server instance to connect to. This can be local or on a network pc. In this case the parameter will have the
PCName\InstanceName format. Default value: (local). Default value for MS SQL Server 2008 Express: .\SQLEXPRESS.
Database: this is the name of the database which will be created in relation to the instance specified in the "server" parameter. If this field is left empty, the database's name will be the same as the project's name.
The plugin uses a "Trusted connection", meaning that it uses Windows authentication. If you wish to use another authentication type, you can modify the ODBC connection manually once created.
Driver: this is the ODBC driver used by Movicon for connecting to the database. Default value: "MySQL ODBC 5.1 Driver".
Server: this is the name of the MySQL instance which to connect to. It can be local or on a network pc. Default value: localhost.
Database: this is the name of the database which will be created in relation to the instance specified in the "server" parameter. If this field is left empty, the database's name will be the same as the project's name.
User and Password: are the name of the user and their password respectively which are used for connecting to the MySQL instance. This data is saved in the settings file without being encrypted. In order to keep passwords secret, they can be inserted using the"Administration tools - Source ODBC" "Control Panel" item after the ODBC has been created.
Driver:this is the ODBC driver used by Movicon for connecting to the database. Default value: "ORACLE in XE".
"Oracle in OraDb11g_home1"
"ORACLE in XE"
Server: this is the name of the Oracle instance which to connect to. It can be local or on a network pc. Default value: XE.
Database: warning: in Oracle the entity underneath where the Movicon data tables will be created it not a database but a "Database user" or "schema" that is created with the name set here relating to the instance specified in the "server" parameter. If this field is left empty, the database's name will be the same as the project's name.
User and Password: are the name of the user and their password respectively which are used for connecting to the Oracle instance. This data is saved in the settings file without being encrypted. In order to keep passwords secret, they can be inserted using the"Administration tools - Source ODBC"" "Control Panel" item after the ODBC has been created.
Check certain limitations regarding: the maximum size of individual Databases, the maximum size of tables (ie. the maximum number of Columns for each individual Table), maintenance needed, RAM occupation etc. in the specific documentation of the DBMS used. |