{"id":426,"date":"2010-10-01T11:49:35","date_gmt":"2010-10-01T10:49:35","guid":{"rendered":"http:\/\/www.penguino.co.uk\/?p=426"},"modified":"2011-07-19T17:07:27","modified_gmt":"2011-07-19T16:07:27","slug":"sage-line-50-odbc-driver-manual-installation","status":"publish","type":"post","link":"http:\/\/www.penguino.co.uk\/computing\/sage-line-50-odbc-driver-manual-installation","title":{"rendered":"Sage Line 50 ODBC driver \u2013 Manual installation"},"content":{"rendered":"\n\n\r\n\n\n\n

NOTE [26 OCT 2010]<\/strong>: The following article will teach you how to extract a Sage ODBC driver from a PC with Sage installed, and then install the extracted driver onto another PC without using the installation CD.<\/p>\n

For Windows 7 users<\/strong><\/span>: I have been receiving many hits on this article from people searching for “Windows 7 installation” of the ODBC driver. The following method will work – though if you happen to have the installation CD and using Windows 7, I would rather recommend you to install it by using the setup CD – but YOU MUST RUN THE INSTALLATION as ADMINISTRATOR<\/span> by right clicking on the setup.exe and choose “Run as Administrator”. You will also need to have either admin privilage or have the administrator’s password to be successful.<\/p>\n

Feel free to leave me a question and I will help you out if you have any problem. \u00a0Now let the journey begins….<\/p><\/blockquote>\n

 <\/p>\n

Recently some so called \u201ccomputer consultant\u201d was working in the office, try to migrate to Windows 7 by installing it on a bunch of PCs without testing. He does not know \/ care \/ forgot \/ cannot find the ODBC driver<\/strong> which was in the older but working XP system.<\/p>\n

\"\"The driver –\u00a0a Sage Line 50 ODBC<\/strong> driver v16<\/strong>, was needed because we use a number of in-house MS Access databases which connect to our Sage accounting system on the file server.<\/p>\n

The account data files had been upgraded to version 16. But the original CD only has the version 15 driver.<\/p>\n

As a consequence, the newly installed Win7 or XP systems don\u2019t have the right ODBC driver, they get the usual \u201cODBC error\u201d and cannot use MS Access to connect to Sage account files.<\/p>\n

To cut a long story short :- without the driver in hand, I need to devise a hack to extract the driver from the working system, and to manually install the ODBC driver back on the new XP and Windows 7 systems.<\/p>\n

<\/p>\n

A few people on the internet were looking for information on how to install ODBC drivers manually (for either Sage or other third party drivers). I found a good guide from this site <\/a> which teaches us to install\u00a0other ODBC drivers. It is a generic solution from a research point of view, and it got me started to use it to work on Sage\u2019s driver. So full credits due to the original article writer.<\/p>\n

Let\u2019s get to the specifics: for Sage Line50, I am going to outline the manual driver installation steps here. I hope it will help someone out there. There are 3 steps to do:<\/p>\n

    \n
  1. Extract the driver file<\/li>\n
  2. Understanding the ODBC in relation to the registry<\/li>\n
  3. Copy the driver file and Tweak the registry<\/li>\n<\/ol>\n

    1) Extract the driver file<\/h2>\n

    Sage Line 50 ODBC driver file is located in the directory %drive%\\windows\\system32<\/strong> There is only one file to copy. As far as I know, from v12 and upwards, the driver file is named SXXDBC32.DLL<\/strong> where XX<\/strong> is the version number.<\/p>\n

    (e.g. in my situation, v16 is S16DBC32.dll<\/strong> and the file was located at C:\\WINDOWS\\system32\\S16DBC32.dll<\/strong><\/p>\n

    \"\"<\/a><\/p>\n

    Once you have located it on another PC which has it\u00a0\u2013 make a copy and keep it safe somewhere (say on a USB stick). We will need to put this into the new PC\u2019s system32 directory later.<\/p>\n

    2) Understanding the ODBC in relation to the registry<\/h2>\n

    OK \u2013 don\u2019t get scared about the registry. It is quite easy so please sit down with a cup of coffee and read on \u2026<\/p>\n

    \"A<\/p>\n

    Sage Line 50 ODBC driver puts 4 entries into the registry. When you open the ODBC administration panel, these entries tell Windows XP, Vista or Win 7 what the driver name is and where it is located. I highlighted the entries as follows:<\/p>\n

    Windows Registry Editor Version 5.00\r\n\r\n[HKEY_LOCAL_MACHINE\\SOFTWARE\\ODBC\\ODBC.INI\\ODBC Data Sources]\r\n\"SageLine50v16<\/span>\"=\"Sage Line 50 v16<\/span>\"\r\n\r\n[HKEY_LOCAL_MACHINE\\SOFTWARE\\ODBC\\ODBC.INI\\SageLine50v16<\/span>]\r\n\"Driver\"=\"C:\\\\WINDOWS\\\\system32\\\\S16<\/span>DBC32.dll\"\r\n\"DataPathname\"=\"c:\\\\sage\\\\sfw\\\\accdata\"\r\n\"UseDataPath\"=\"No\"\r\n\r\n[HKEY_LOCAL_MACHINE\\SOFTWARE\\ODBC\\ODBCINST.INI\\ODBC Drivers]\r\n\"Sage Line 50 v16<\/span>\"=\"Installed\"\r\n\r\n[HKEY_LOCAL_MACHINE\\SOFTWARE\\ODBC\\ODBCINST.INI\\Sage Line 50 v16<\/span>]\r\n\"UsageCount\"=dword:00000001\r\n\"Driver\"=\"C:\\\\WINDOWS\\\\system32\\\\S16<\/span>DBC32.dll\"\r\n\"Setup\"=\"C:\\\\WINDOWS\\\\system32\\\\S16<\/span>DBC32.dll\"\r\n\"CPTimeout\"=\"<not pooled>\"<\/pre>\n
    You can download and save this file to your system, and you can use notepad to edit it. Or you can copy and paste it the above into your own editor.<\/p>\n
    You can see that I am using v16 driver. So if you are using other versions, you will need to replace the word \u201cv16\u201d with your version number, and also rename the driver name S16DBC32.dll with your version number.\u00a0 (coloured in red below)<\/p>\n
    \"Sage<\/a><\/p>\n
    Once you are done, save the file with the extension .reg\u00a0\u00a0 (I called mine SageOdbc.reg) and keep it on your USB drive together with the driver file that you extracted earlier in Step 1.<\/p>\n
    3) Copy the driver file and Tweak the registry<\/h2>\n
    Well you have actually done the hardest part. So now take your USB to the new computer that needs the driver.<\/p>\n