The ODBC driver is no longer part of the base product. It can be purchased separately with each annual upgrade. You can purchase the driver from the “My Account” page by logging into our website using your serial number, billing zip/postal code and email address.

My Account Page

Using AccountEdge and ODBC

The AccountEdge ODBC connection is a one way connection. The connector is designed to export the information from AccountEdge other programs using the ODBC connector, but it will not allow information to be imported into AccountEdge. For information on importing into AccountEdge using Comma-Separated and Tab-Delimited text files please see this article.

Documentation

Additional documentation for the ODBC AccountEdge connection is available in the ODBC User Guide. This manual also includes information on the tables and fields available to ODBC clients. The information in this manual is for AccountEdge 2020 US specifically but is applicable to most other versions.

Supported Versions

ODBC support is provided for the current and two previous versions of AccountEdge Pro. 

General

The ODBC Direct driver is installed automatically when AccountEdge is installed on a Windows platform. (If need be, the ODBC Direct driver can be reinstalled using the custom installation option.) To install, configure and test ODBC, follow the 3 steps listed below.

Driver Location:

C:\MYOBODBC[Country][Year]

[Country] is either US or CA depending on whether you use the US or Canadian version. [Year] is the two digit year (ie: 11 for AccountEdge 2011)

Step 1: Installing ODBC for company file access

With AccountEdge Pro 2012, and later, this step is unnecessary. The ODBC Driver is automatically installed. But if the folder (indicated above) is missing, you will need to install the ODBC Driver.

The installation wizard for the ODBC driver is installed with AccountEdge Pro. Run the installation wizard to install the driver.

Installation Wizard Location:

AccountEdge 2011: C:\AccountEdge2011\ODBCDirect11\setup\ODBC  
AccountEdge 2012 and Later: C:\AccountEdgePro[Year]\ODBCConnect[Version]\setupODBC

[Year] is the full 4 digit year (ie: 2016)  
[Version] is the 2 digit year (ie: 16 for AccountEdge 2016)

• Step 2 for XP Platforms
• Step 2 for Windows Vista and Later 32 Bit Platforms
• Step 2 for Windows Vista and Later 64 Bit Platforms

Step 2: Configure ODBC (XP Platform ONLY) for company file access

To setup the connection:

1. Click on the Start Menu, and open up the Control Panel.
2. Click on Administrative Tools.
3. Double click on Data Sources (ODBC). That will bring up the ODBC Data Source Administrator. There are tabs for User DSN, System DSN, and File DSN. Either the User or System DSN can be used. User DSN is created per user on the computer, and the data set can only be accessed by that user. A System DSN is per system and is accessible to all users. The user should be logged in to the machine as the Administrator when connections are configured.
4. Select the appropriate tab, and click Add; then scroll down the list and choose MYOUS1201.
5. Click Finish.
6. On the next window, enter a Data Source Name and the Description.
7. When those fields are filled in, click on Browse to Company File Path, and navigate to and select the AccountEdge Company File to be connected.
8. Enter a User ID and a Password. Click OK.
9. The Data Set is ready for ODBC access.

Step 2: Configure ODBC (32-bit Vista & 32-bit Windows 7 Platforms ONLY) for company file access

On 32-bit systems: To setup a connection:  
Go to the bin\iwinnt folder in the ODBC Driver folder

C:\MYOBODBC[Country][Year]\bin\iwinnt

[Country] is either US or CA depending on whether you use the US or Canadian version. [Year] is the two digit year (ie: 11 for AccountEdge 2011)

In that folder, execute (double-click) the the Windows-based RDA Administrator (wrdadml.exe)

1. Click the ODBC Administrator button.
2. Double click on Data Sources (ODBC). That will bring up the ODBC Data Source Administrator. There are tabs for User DSN, System DSN, and File DSN. Either the User or System DSN can be used. User DSN is created per user on the computer, and the data set can only be accessed by that user. A System DSN is per system and is accessible to all users. The user should be logged in to the machine as the Administrator when connections are configured.
3. Select the appropriate tab, and click Add; then scroll down the list and choose MYO[Country][Year].
4. Click Finish.
5. On the next window, enter a Data Source Name and the Description.
6. When those fields are filled in, click on Browse to Company File Path, and navigate to and select the AccountEdge Company File to be connected.
7. Enter a User ID and a Password. Click OK.
8. The Data Set is ready for ODBC access.

Step 2: Configure ODBC (64-bit Vista, 64-bit Windows 7 & 64-bit Windows 8 Platforms ONLY) for company file access

To setup a connection:

1. Open the C:\WINDOWS\SysWOW64\ folder on your hard drive and double-click the odbcad32.exe file.
2. There are tabs for User DSN, System DSN, and File DSN. Either the User or System DSN can be used. User DSN is created per user on the computer, and the data set can only be accessed by that user. A System DSN is per system and is accessible to all users. The user should be logged in to the machine as the Administrator when connections are configured.
3. Select the appropriate tab, and click Add; then scroll down the list and choose the latest driver (e.g., MYOBCA1303 or MYOBUS1301).
4. Click Finish.
5. On the next window, enter a Data Source Name and the Description.
6. When those fields are filled in, click on Browse to Company File Path, and navigate to and select the AccountEdge Company File to be connected.
7. Enter a User ID and a Password. Click OK.
8. The Data Set is ready for ODBC access.

Step 3: Testing the ODBC Connection

Test Connection (TestConnection.exe) is the utility used to test ODBC connections. Its location is:

C:\MYOBODBC[Country][Year]\bin\iwinnt

[Country] is either US or CA depending on whether you use the US or Canadian version.  
[Year] is the two digit year (ie: 11 for AccountEdge 2011)

To run the test connection:

1. Double-click on TestConnection.exe
2. On the Test Connection, make sure the default option on the top left is set to DSN. Also the driver to the right of that, should be set to the current driver.
3. After choosing the correct options on top, next to MYOB Data Source name (DSN) click on the correct data source.
4. Click on test.

This will test the connection and show as to whether the connection to the file has passed or failed.

Connection Strings

You can connect to, and read from, an AccountEdge company file with or without configuring an ODBC User data source for the file. You can also modify the way you connect by using connection strings. Information about connection strings provided in this section will only be useful if you have an advanced knowledge of ODBC and connecting to data sources.

Connection strings can be used to override values set in the data source configuration, or to establish a company file connection without having to set up an ODBC User data source and Data Source Name (DSN). A connection string is not required for read operations where a DSN has been set up for an AccountEdge company file.

Connection String Keywords

Parameters within the connection string, defined by keywords and their assigned values, override the default ODBC User data source values. A connection string is a concatenation of a number of keywords and assigned values in the format [KEYWORD]=[VALUE]; keyword and assigned value statements are separated using a semicolon, and terminated using a semicolon.

Connecting to a Company File

Using the DRIVER keyword set with the value DRIVER={MYOUS2013} you can connect to a company file without the need to set up an ODBC User data source for the file.

When connecting to a company file for reading purposes without using an ODBC User data source, the following keywords must be set:

Type=MYOB;  
UID=<user ID>;  
PWD or PASSWORD=<password>;  
DATABASE=<path and name of company file>;  
HOST_EXE_PATH=<path and name of application>;

A number of optional keyword values are available. See the ODBC User Guide.

Example Connection String

"Driver={MYOUS1401}; TYPE=MYOB; UID=Administrator; PWD=MyPassword; DATABASE=C:\Documents\AccountEdge Pro 2014 US\myFile.myo; HOST_EXE_PATH=C:\AccountEdgePro2014\AccountEdge.exe; NETWORK_PROTOCOL=NONET; DRIVER_COMPLETION=DRIVER_NOPROMPT; ";

Notes on Access

ODBC Access

Due to changes in the software that we license to provide ODBC access to company files, a user will not be able to access a company file from a server running Windows 2000 or 2003 Server operating system. Although the user can host the file on a server running Windows 2000/2003 Server, the user will not be able to install and use the ODBC Direct software on that machine to access the file. Users can however, connect to the file over the network using another computer with ODBC Direct installed.

ODBC with 64-bit Server

A 32-bit OS will run system32\odbcad32.exe to bring up the ODBC Data Source Administrator Window which lists all the Drivers, DSN's. etc. Where as a 64-bit OS will run odbcad64.exe. In order to see the 32-bit ODBC driver in the 64-bit version of MS Vista, you will need to run odbcad32.exe. This can be done from the Run Command Window.

64-Bit Windows

The installation and configuration instructions explain how you can set this up. If you have trouble regarding this - you want to follow the instructions below.

If you go to the ODBC Data Source Administrator via Control Panel/Administrator Tools, you may not see the AccountEdge MYOUS1601 driver. This is because there are two ODBC Data Source Admin utilities that can be run depending on if the OS is 64 or 32 bit.

When adding a DSN entry for AccountEdge and you do not see the MYOUS1601 driver in the list as seen below, then you should exit this ODBC Data Source Admin and find the admin in the SysWow64 directory.

Find and launch this version of the ODBC Admin found in the C:Windows\SysWOW64 directory.

This one found in C:\Windows\System32 may not display the MYOUS1601 driver depending on if you are running the 64 or 32 bit version of Windows.