Hi RandyW,

The best people to answer this question would be our development team. Support is provided by email only to our development partner; however, if our development team determines that there is a need to communicate with the customer over the phone, they will call them.

If you are using our Development kit and are not yet registered as a development partner you can do so by emailing [email protected].

Hope this helps!

Thanks Keith,

I'm aware of the support options for development partners, but thought that this was more of a Microsoft Access issue.  

Perhaps instead, it's a problem with the custom MySQL 5.2(a) ODBC driver that the Development Support team would know about..  

My question was really related to whether anyone else was having brand new problems with Access 2013, and creating new linked databases for reporting or other purposes, since installing the 2014 release.

Databases created in Access 2013, with the 2013 Sage 50 releases (MySQL ODBC 3.51) still work properly with the 2014.2 release, after deleting all the existing ODBC connections on the workstation and allowing them to be created on login to Sage 50 2014.

Storing the password in the Access 2013 file doesn't seem to work with a new database, created after installing Sage 2014.

Maybe I'm the only one using Access and ODBC?

I presume the standard MySQL ODBC 3.51 driver is used to connect to Sage

is there a document which identifies what the connection string looks like ?

Databases that were linked using the old MySQL ODBC 3.51 driver (up to Sage 50 2013.2)  continue to work fine.

Databases created since the installation of 2014.1 have not worked properly, although the older ones started working once the older 3.51 ODBC items were removed.

Sage automatically creates 3 types of ODBC connection as USER DSNs when you open a company 'file' in Sage 50 from a workstation.  If you look in the ODBC manager you should see all these connections.

The old Windows ODBC.INI information is now stored in the Registry. 

Open RegEdit, search for ODBC.INI.  I found connection information in:

HKEY_USERS\S-1-5-21-2871204426-55922388-3136739366-1133\Software\ODBC\ODBC.INI\Sage 50: Last opened.

For instance, the Driver for the above ODBC connection is:

C:\Program Files (x86)\MySQL\Connector ODBC 5.2\ANSI\myodbc5a.dll

You could search for that, too.

the SID part of the path will of course be different.

I am having the same problems - losing the connection in MS Access.  The only way to get it back is to close MS Access and go back in, reconnect using the Linked Table Manager and then re-entering my login info and password again.  Very inconvenient, to say the least.

Has anyone found a solution yet?

Hi,

The best work-around suggestion I've seen, was to:

- allow Sage 50 to create the ODBC DSN, then

- open the DSN in the 32 bit version of the ODBC manager and add the user name and password permanently to the DSN.

- That ODBC connection should now work with Access.

I think the problem may be related to running a 32 bit ODBC connector under a 64 bit O/S.   It doesn't seem to store the password for some reason.  

Adding the password to the ODBC connection isn't really a good solution for building reports or utilities to hand off to someone else on another workstation, or for a shared workstation, and may not work with a roaming network profile.  But it did the job for what I needed.

I hope that helps, please post back.

Thanks a lot, Randy!  That worked.  I am on a 64 bit o/s, and by adding the user name/password thru the 32bit ODBC administrator as you suggested, I no longer lose my connection.  I am the only one using this machine, so I am not worried about anyone else accessing this database.