Linking the Workbench Program File

Owned by Former user (Deleted)
Last updated: Aug 22, 2012


The Workbench program file is a Microsoft Access .mde file.

This file is installed on each workstation (or the Citrix / Terminal Server machine if used). Before installing on the workstations, this .mde file needs to be 'linked' to the SQL Server Workbench database

  • Open the directory Workbench\Setup\Server Setup
  • Uncompress the file called Workbench721_ProgramMDE.zip into a new directory under the same location
  • Open the directory created in the step above. In it you will find a file called TcwbXXXX.mde, where XXXX is the version of workbench you are installing
  • Copy this file
  • Navigate to the Workbench\App directory. Here you will find a list of directories with the same names as the Workbench instances that have been set up. In this case Live and Test.

 

  • Paste the file in to each of these directories
  • Open the first of these directories and it will display the file you have just copied.
  • Click on the file once so that it is highlighted. While holding the shift key down double click the file. Continue to hold the shift key down until you are sure the file is open
  • If you have Access 2003 select the Macros tab.
  • If you have Access 2007 select Macro's from the Drop down box on the side bar as displayed below

 



Find the macro called ChangeConnectString

  • Clicking this will display this screen

 

 

  • In the SQL Server name type in the name of your SQL server. Make sure you use capitals where necessary.
  • Fill in the Database with the database name of the Workbench instance you are linking. i.e. if you are in the Live directory the database should be called WorkbenchLive.
  • Click the Re-Link Tables button

 

After a few minutes you should get the following message:

 

 


Re-linking Errors
Some configuration issues that can prevent re-linking are:

  • Firewall on Server that SQL server is installed on is turned on and does not have an exception for port 1433
  • Firewall on the local machine is turned on and does not have an exception for port 1433
  • Firewalls doe have exceptions for 1433 but still need to be turned off for the connection to work. Contact you IT provider to discuss options for this case.