MagTek IntelliCAT99875658 User Manual
Page 9
<IntelliCAT>| <Migration to Windows 7> | <User Support Document>
Page 9
12 E
- Controller UDL's, if in use, may have different names
UDL's for WorkQConnect - examples are Controller.UDL, Work.UDL, Production.UDL, etc. and are only
required in a Networked Environment.
Typical examples of the path structure to the WorkQConnect as located in the [ODBC] section are:
Local
Controller UDL’s local path structure
Action Required
(32 bit)
WorkQConnect="File Name=C:\Program
Files\MagTek\IntelliCAT\Controller.UDL"
No change required.
(64 bit) –
WorkQConnect="File Name=C:\Program Files
(x86)\MagTek\IntelliCAT\Controller64.UDL"
Create a new Controller64.UDLfollowing the
same steps as referenced in
Step 12
B
.
Change the name in the path structure in the
[ODBC] section of the Desktop INTCAT.INI file to
reference the new Local Controller64.UDL
Networked
Controller UDL’s Networked Path Structure
Action Required
(32 bit)
WorkQConnect="File
Name=\\server1\MagTek\IntelliCAT\Controller.UDL"
No change required.
(64 bit)
WorkQConnect="File
Name=\\server1\MagTek\IntelliCAT\Controller64.UDL
Create a new Controller64.UDL for the Network
following the same steps as referenced in
Step 12
B
.
Change the name in the path structure in the
[ODBC] section of the Desktop INTCAT.INI file to
reference the Network Controller64.UDL. In this
environment, the old Controller.UDL will be used
during the migration process.
Typical connections strings for most Controller UDL's when using MtAdmin.MDB
For the Controller.UDL, it will point to:
C:\Program Files\MagTek\IntelliCAT\MtAdmin.
MDB(32bit)
For the Controller64.UDL, it will point to:
C:\Program Files (x86)\MagTek\IntelliCAT\MtAdmin.
MDB (64bit)
Note: A Controller.UDL may be in use if a SQL Server is being used but it not required as long as
each Controller PC has, as an example, a unique CGSName=”Branch1” in the [Startup] Section
and it also have a ServerName=”Branch1” in the [Controller] section. If the Default Controller is
used for the CGSName and ServerName respectively, then a Controller.UDL and a
Controller64.UDL is mandatory and the connection string must point to the appropriate database
as noted above. (O.S. dependent).