By using this web site, you agree to all terms and conditions for acceptable use.

ServiceLedger KnowledgeBase Knowledgebase Home Page > ServiceLedger > Technical | Contact Us

Search the Knowledge Base Browse by Category

ServiceLedger provides this content as-is for self help support purposes. ServiceLedger assumes no liability for any steps you take based on the directions in our knowledge base, and assumes that you have the knowledge to determine whether a given step is appropriate for your situation. Certain solutions can affect third-party software that ServiceLedger relies on or integrates with; it is your responsibility to consult with the documentation or publishers of such third-party software to understand whether any changes suggested here will have negative effects on other applications.

(T0140) How do I set up a workstation to access multiple databases?

Would you like to...

Print this page
Email this to a friend

If you need to set your SERVER up with multiple versions or databases, DO NOT USE THIS DOCUMENT. Instead, please see the following KB article for assistance:

(T0135) How do I set up my server with multiple databases?

Please use these directions to set up a workstation (client) to access different versions of ServiceLedger or different ServiceLedger databases.


Before beginning, you will need to know the following information for each of the databases you plan to connect to:

  1. Server Name - The name of the machine that is hosting the database
  2. Instance Name - If the database is hosted by a named instance of SQL server, you must know the instance name. In a default installation, this is "ServiceLedger".
  3. Database Name - The name of the database. In a default installation, this is "ServiceLedger", however it is common in multi-database setups to have names such as "ServiceLedger_Commercial" or "ServiceLedger_Old55", etc.
  4. Identifier - For each database, you should choose an identifier you will consistently use when naming similar files for multiple databases. Consistent with the example above, it would be best to use identifiers such as "_Commercial" and "_Old55". Important: Identifiers MUST ALWAYS begin with an underscore (_)

This information will be used throughout this document and referred to as [ServerName], [InstanceName], [DatabaseName], and [Identifier] for items 1, 2, 3, and 4 respectively. If in any directions you see the above, you should replace the name and brackets with the actual value.

For example, let's say you have a database server called SLServer hosting a database called ServiceLedger_Test in the ServiceLedger instance and you've chosen _Test as your identifier. If you are asked to type:
  -odbc ServiceLedger[Identifier] -server [ServerName]\[InstanceName]
you would instead type:
  -odbc ServiceLedger_Test -server SLServer\ServiceLedger


First, and only once per machine, you should install ServiceLedger normally and allow it to connect to your server normally. To do this, use the following steps:

  1. Download our installer or copy it from another computer on the network (contact ServiceLedger Support if you need the installation file).
  2. Run the installer normally, choosing the Workstation Only / Advanced option
  3. Enter the server name when prompted to do so. If you have multiple server machines, enter the name of whichever one has a database called ServiceLedger. If multiple database servers have a ServiceLedger database, pick either one. If none of your database servers have a database named ServiceLedger, please contact for special assistance.
    If the database configurator cannot establish a connection to the server, but you are certain that the server you're typing in exists and has a ServiceLedger database, try disabling any network firewalls or computer firewalls on your server or client. Also verify that you can ping the server name from a command prompt.
  4. During the install, both the Updater and ServiceLedger will launch. This is normal.
  5. Once the install is complete, click the Close button to exit the installer.

After installing, verify that ServiceLedger is installed properly by launching it and making sure that it is showing data from the ServiceLedger database on whichever server you chose. You can do this by opening ServiceLedger with that database on the server, making some changes, and then checking to see if those changes are present on the workstation after a refresh.

Once ServiceLedger is properly installed on the workstation, repeat the following steps FOR EACH DATABASE you need the workstation to connect to. As mentioned above, you will need to know the server name, instance name, database name, and identifier FOR EACH DATABASE.

  1. Create a folder for this copy of ServiceLedger. To do this, use the following steps:
    1. Open the main ServiceLedger folder,
    2. For 32-bit machines:
    3. C:\Program Files\ServiceLedger\ServiceLedger
    4. For 64-bit machines:
    5. C:\Program Files (x86)\ServiceLedger\ServiceLedger
    6. Verify that there is no folder called MSDE in your main ServiceLedger folder. If you have such a folder, you have probably performed a Server / Evaluation install on this machine and will need to uninstall MSDE before continuing.
    7. Go up one folder in the hierarchy, to C:\Program Files\ServiceLedger
    8. Copy and paste the ServiceLedger folder, then rename the Copy of ServiceLedger folder to ServiceLedger[Identifier]. For example, if your identifier is test, you would rename this folder to ServiceLedger_Test.
    9. There should now be TWO ServiceLedger folders under PROGRAMFILES\ServiceLedger, 1) PROGRAMFILES\ServiceLedger\ServiceLedger, and 2)PROGRAMFILES\ServiceLedger\ServiceLedger_Test, both of which should have identical files.
    10. Go to the folder you just created, C:\Program Files\ServiceLedger\ServiceLedger[Identifier]
    11. In this folder, you will need to create a file called ServiceLedger.ini. Open this file with Notepad or your text editor of choice. Important: In order to create ServiceLedger.ini, you will need to make sure that Windows is showing file extensions for known file types:

      Windows XP: Open Windows Explorer, go to Tools > Folder Options > View, then uncheck "Hide extensions for known file types; click OK"

      Windows Vista and later: Open Windows Explorer, click on Organize > Folder and Search Options > View, then uncheck "Hide extensions for known file types; click OK"

    12. Serviceledger.ini should have two lines only. The 1st line should read:


    13. The second line should read (without quotes): "DSN=ServiceLedger[Identifier]". If '_Test' is your Identifier, the second line should read:


    14. Save the ServiceLedger.ini file and close your text editor.

  2. Create an ODBC System DSN for this copy of serviceledger. To do this:
  3. For 32-bit machines:

    1. Open Control Panel. (Start -> Control Panel or Start -> Settings -> Control Panel)
    2. If Control Panel shows categories instead of icons, click on the Switch to Classic View task in the left pane of your control panel window
    3. Double-click on the Administrative Tools icon
    4. Double-click on the Data Sources (ODBC) icon
      The ODBC Data Source Administrator window should appear

    For 64-bit machines:

    1. Open Windows Explorer and navigate to C:\Windows\SysWOW64
    2. Find odbcad32.exe and double-click it or hit Enter when it is selected to open the ODBC Data Source Administrator window

    To create the ODBC entry for your additional ServiceLedger database:

    1. Click on the System DSN tab
    2. Click the Add button, on the right
    3. In the list of drivers, choose SQL Server. It should appear at or close to the bottom of the list
    4. Click the Finish button
      The Create a New Data Source to SQL Server window should appear.
    5. In this window, fill in the Name box with ServiceLedger[Identifier].
    6. Leave the Description box blank
    7. Fill the Server box with either [ServerName], if you have no instance, or [ServerName]\[InstanceName] if you have an instance. Note the single backslash ( \ ) between the server and instance name.
    8. Click Next
    9. In the next page, select the With SQL Server authentication... radio button, unless support or your network administrator have instructed you otherwise.
    10. If you have With SQL Server authentication... selected, type in your SQL Server Login ID and Password. Unless you have been instructed otherwise by your network administrator or ServiceLedger Support, these will be sa for the Login ID and s1d#m0*1S1Sl for the Password.
    11. Click Next
    12. Make sure the Change the default database to checkbox is checked
    13. In the box below, choose the database named [DatabaseName]. If you do not see the database you're looking for, verify that you have the correct server and instance name in the first page of this wizard. If these are correct, verify the server name, instance name, and database name with your network administrator or ServiceLedger Support.
    14. Click Next
    15. Click Finish
    16. In the ODBC Microsoft SQL Server Setup window that appears, click Test Data Source... and verify that it shows the message TESTS COMPLETED SUCCESSFULLY!
    17. Click OK a final time to return to the ODBC Data Source Administrator
    18. Verify that you see a data source with the name ServiceLedger[Identifier] in the System Data Soruces list
    19. Close the ODBC Data Source Administrator and Control Panel windows
  4. Create a Desktop shortcut to this copy of ServiceLedger. To do this:
    1. Open the ServiceLedger folder for this copy, C:\Program Files\ServiceLedger\ServiceLedger[Identifier]
    2. Find the ServiceLedger.exe program
    3. Right-click ServiceLedger.exe and choose Send To > Desktop (create shortcut)
    4. Close the ServiceLedger folder and close and/or minimize any other running programs so that you can see your Desktop
    5. Rename the new Shortcut to ServiceLedger.exe shortcut to ServiceLedger[Identifier]
    6. Double-click ServiceLedger[Identifier] and verify that ServiceLedger opens successfully and that it is connecting to the correct database.

After performing these steps, return to the top of this numbered list and repeat for the next database, using the next set of server name, instance name, database name, and identifier.

Once these steps have been performed for all databases, workstation setup is complete. You should have a shortcut on your desktop to run ServiceLedger for each database. You may optionally remove the default shortcuts to ServiceLedger from your start menu.

Related Questions:


No attachments were found.

ServiceLedger KnowledgeBase Copyright © 2020
Powered by AcitveKB Knowledgebase Software