Support Home Sales Website Technology Contact Us
RDP Support  

RDPWin KB Booking Engine - IRM.Net RDPWin4 & PCI Compliance Search

Manual ODBC Connection for Updating to RDPWin Version

Article ID: KWin0040
Updated:  01/31/13


The first time you run RDPWin Version you will be prompted with the Administrator Logon screen this screen sets up the ODBC connection on the Pervasive data server and is needed to successfully run RDPWin Version

Enter the password for the Administrator and click OK.  If this process fails, this screen will continue to be displayed and the customer should contact RDP Support immediately at 970-845-7108.

Steps for Pervasive 9.0 or higher users

Steps for Pervasive 8.7 users

Steps Using ODBC Administrator

Pervasive's website offers the following link for

Error 1918. Error Installing ODBC driver.

Steps for Pervasive 9.0 or Higher Users

  1. Login to the RDP Data server and set Registry for Pervasive access  See K000163.HTM
  2. Go to Start/Programs/Pervasive/Control Center.
  3. Expand Engines.
  4. Expand "Server".
  5. Right-click on Database and select New, then Database as shown here.

    At the New Database screen:
  6. Enter the Database Name as RDP01.
  7. Enter the Location as "c:\RDPNT"  (Location of DDFs).
  8. Bound should NOT be checked.
  9. "Create dictionary files" should NOT be checked.
  10. "Relational integrity enforced" should NOT  be checked.
  11. "Create Engine DSN" should be checked.
  12. Click Finish.
  13. Right-click the new connection that was created and select Properties.

  14. In the Properties window, click Remove to eliminate the directory listed in the Data Directories section.

  15. Click the New button, enter the path shown below, and click OK.

  16. The Properties window should display as:

  17. Click Apply.
  18. Click OK.
  19. If connections issues still occur, see Pervasive 10 ODBC Connection Issue.

Steps for Pervasive 8.7 Users

  1. Login into the data server & Set Registry for Pervasive interface  See K000163.HTM.
  2. Go to Start/Programs/Pervasive.sql8/Control Center.
  3. Expand Engines.
  4. Expand "Server".
  5. Right-click on Databases (Engine) and select New DataBase....
  6. Fill in the Name field with the name of the RDP directory you are creating the OBDC connection.  For most customers this will be RDP01.
  7. Fill in the Directory field with the path to the RDP directory.  You must use the UNC path.  For example: \\"rdpdataserver"\rdpnt\rdp.
  8. Check "Use advanced settings".
  9. Click the Next button.
  10. Verify that all fields on the "Create Database Wizard for Pervasive.SQL" match the sample screen below:
  11. Click the Create button (located next to the "Database name" drop-down) to create a new DSN (Data Source Name).
  12. Check "Integrity enforced".
  13. Uncheck "Bound (DDF created)".
  14. Set "Betrieve security policy" to Classic.
  15. Change "Dictionary location" to the location of .DDF files (Data Dictionary Files).  For example:  \\'rdpdataservername'\rdpnt\rdp.
  16. Verify the data file location is correct.  The location should be where the RDP data files are filed.  For example:  \\'rdpdataserver'\rdpnt\rdp\rdp01.
  17. Click OK, and then Next.
  18. Verify all information is correct, and click Finish.  The database should be successfully created.
  19. Click Close.

Use ODBC Administrator to Create ODBC Connection

  1. Login to the RDP Data server & set Registry for Pervasive  See K000163.HTM
  2. Control Panel, Administrative Tools, Data Sources (ODBC).
  3. Click the System DSN Tab.
  4. Click the Add button.  Note: If RDP01 exists and you are still having problems, see Correcting Pervasive Java Error K-Base Article.
  5. Select "Pervasive ODBC Engine Interface".
  6. Click Finish to open the Pervasive ODBC Engine Setup Screen.
  7. Set following fields:
    1. "Data Source Name" - RDP Directory (i.e., RDP01).
    2. Description - leave as default.
    3. Click the Create button.
  8. At the Create Database screen (shown below):

    1. Database Name = RDP Directory (i.e., RDP01).
    2. Integrity Enforced = UNCHECKED.
    3. Bound (DDFs Created) = UNCHECKED.
    4. Btrieve security policy = Classic (OS authentication and authorization).
    5. Dictionary Location = C:\RDPNT\RDP or RDP root directory location.
    6. Data File Locations = Delete current location and add the following:
      1. C:\RDPNT\RDP\RDP01 or corresponding RDP Data folder.
      2. By default, the data dictionary location is added, RDP's data is one level deeper. This is why the original entry is deleted and re-added.
    7. Click OK.
  9. Click the Test button to make sure the connection can be made. (This can take several seconds).
  10. Click OK at the "Connection Successful" prompt.
  11. Click OK.
  12. Click OK to complete the process.
  13. Check DNS using NSLookup on the workstation if the workstation gets the ODBC error and the ODBC connection is correctly setup on the server.

    1. Open a command prompt (from the Start menu, select Run).
    2. Type in NSLookup and click OK.
    3. Enter the server name.  The system should reply with the IP address, or enter the IP address to get the computer name.

ODBC Connection Problem with Pervasive 10?

How do I turn off Data Execution Prevention Errors?

  1. Check the RDPWinPath.txt file.  Confirm the path is correct.  If it is a client computer, make sure it is using the UNC path.
  2. Open Pervasive control center and verify the Database (canister) RDP01 exists with the correct dictionary location and data directory paths. This is usually the problem.
  3. Go to ODBC source administrator and verify the System DSN RDP01 exists.
  4. Run the pervasive system analyzer. The relational test should point to the RDP01 DSN.  If this passes, go to Step 5.  If it does not pass, skip to Step 7.
  5. Verify the RDP01 tables are visible in the Pervasive Control Center. If not, skip to Step 7.  Otherwise, continue with Step 6.
  6. Run a select statement in Pervasive Control Center on a small data file in the RDP01 directory. If this passes, try to restart RDPWin.
  7. Delete the System DSN in ODBC Data Source Administrator, and Delete the RDP01 database in Pervasive Control Center.
  8. Reboot.
  9. Add the RDP01 database with the correct Dictionary and Data Directory paths in the Pervasive Control Center.  Verify that the DSN exists in Data Source Administrator.
  10.  Repeat Step 5 & 6.
  11. If all fails, call RDP Support and/or reload pervasive.
Support Home  RDPWin4 & PCI Compliance Enhancement Requests Open A Web Support Ticket
Training New Sales Website Old Sales Website Contact Us

 Facebook     Twitter      LinkedIn   TODF