Easy Way to Fix ODBC SQL Server Driver Incorrect Precision Error

Microsoft Business Arrangements Navision is primary ERP application for European, Brazilian business sectors in addition to it serves vertical fragments of the USA market, like light assembling, POS, CRM. As our experience demonstrates – Navision execution requires more customization and tuning in contrast with another mid-market ERP arrangement from MBS: Microsoft Incredible Fields. We want to promote Microsoft Business Arrangements items and edify IT individuals to do alter Navision in-house. Today, the primary subject of this article is working with local C/SIDE Navision Accomplish information base by means of C/ODBC interface, specifically – Connected Server creation in Microsoft SQL Server 2000 climate and afterward Business chart plan in Gem Reports ver. 10. How about we start:

  1. We will utilize Navision Achieve 3.6 with Navision Data set Server, Navision Application Server and Navision Client. These parts are introduced on Windows XP Proficient. To empower C/ODBC interface you want to introduce this part from Navision Achieve Disc.
  2. We should make ODBC DSN for association with Navision information base: Begin – > Control Board – > Authoritative Apparatuses – > Information Sources ODBC, then change to Framework DSN and click Add. We will utilize C/ODBC 32-cycle driver. Give Information Source Name Navision, Association – leave it Neighborhood. As the information base Data set button select \Program Files\Navision Attain\Client\database.fdb this is demo DB. Then, at that point, press Organization button – for our situation we use CRONUS demo information base. Significant circumstances to furnish appropriate association with C/SIDE information base are right choices for C/ODBC. Click Choices button and take a gander at the choices accessible – we will focus on Identifiers screen – this is where you arrangement identifiers to be moved to client application. We will utilize these sorts: a-z, A-Z, 0-9, _ to make MS SQL Server 2000 work right with C/ODBC source. We are currently finished with ODBC DSN.
  3. Open SQL Server Undertaking Supervisor. Open item program on the left side, select Security and Connected Servers. With right snap select New Connected Server in the setting menu. In the arising exchange window, in the menu Supplier Name select Microsoft OLE DB Supplier for ODBC Drivers. We should name our Connected Server as NAVISION and Easy way to fix odbc sql hy104 server driver incorrect precision error microsoft. In the Information Source string type in ODBC DSN name – NAVISION for our situation. Connected Server is prepared. Select tables rundown and we currently see Navision Accomplish tables.

To explain its text: TRACEON8765 mandate permits working with the information consequences of variable length returned by C/ODBC driver. On the off chance that we do not utilize this mandate – we cannot pull the outcomes from Navision tables.