Requirements for the OLE DB provider

Requirements

  • Correctly installed WinCC OA version
  • Use of the History DB
  • An OLE DB consumer (for example, Crystal Reports, MS Excel) is useful when wanting to address the OLE DB-Provider easily (it can be accessed via any VBA-compatible software by means of ADO access using VBA).
  • At least the Data Manager must be running when the OLE DB Manager is started. If the Data Manager closes, then no more queries are possible.
Attention: Note that only historical data (HDB) can be queried.

Installation

A standard installation of WinCC OA is required for using OLE DP provider.

For more details on installing WinCC OA, see the Installation chapter of the Online Help.

Under Windows 64 bit:

  1. Add the WCCOAoledb manager entry to the progs file under WinCC_OA_Project_Path/config

    windows/WCCOAoledb | manual | 30 | 2 | 2 |

    Note: The WCCOAoledb manager entry has to end with the | sign. Take care that there is no "blank" at the end of the line!
  2. Register the following components as an Administrator user by using the Command Prompt. Before registering the components, switch to the WinCC_OA_Installation_Path/bin/windows directory. Note that you register the components in the given order:
  • WCCOAoledb.exe /regserver
  • regsvr32 WCCOAOleDbExeps.dll
  • regsvr32 WCCOAoledb.dll
Note: The name of the provider is WCCOAoledb OLE DB Provider and that the provider is 32 bit. Therefore, you have to add the manager to the progs file of your project under Windows 64 bit.

Limitations

  • Under Windows 64 bit the OLE DB provider is only supported for single server systems, meaning that the OLE DB manager (WCCOAoledb) runs on a single server system where the proxy runs on the server project. The OLE DB manager is not supported for redundant systems.
  • Data cannot be edited (read-only access)
  • No previous values (only archived DPEs)
  • No queries across distributed systems. The OLE DB provider can only query data from the system on which it is running. The Provider connects itself to the "local" ValueArchive that only contains data from "its own" system.
  • No direct support of Excel 2000 or earlier versions (an example of data access via OLE DB using Excel 97/2000 is supplied with the version.