PDA

View Full Version : ODBC Drivers



  1. ODBC: Failed to get users profile list: [ExA018] client.authorizationError
  2. How to Specify TempFeatures on the AIS Connect String
  3. Issue with Attunity OPTIM Thin Client 3.5
  4. SQL SERVER LINKED SERVER TO ATTUNITY GETTING DISCONNECTED INTERMITTENTLY(very urgent)
  5. Thin ODBC Client
  6. [S1000] [9013]General error in Nav_init - rc = -507
  7. Work with Turkish language and Data Integrator with the Attunity ODBC interface
  8. SAMPLE: ODBC Test and Troubleshooting utility
  9. SAS access AIS ODBC datasources through AIS thinclient
  10. HOW TO: Config AIS ODBC thinclient datasource under Unix ODBC manager
  11. Jbase and Attunity
  12. HOW TO: Business Objects Data Integrator and Attunity Thin ODBC checklist
  13. Executing many SQl statements in ODBC
  14. ODBC driver connecting to UNISYS
  15. HOW TO: Troubleshoot Business Objects Data Integrator processes
  16. HOW TO: Create a simple Data Flow in Business Objects Data Integrator XI
  17. Troubleshooting ODBC Drivers (ODBC Tracing)
  18. Windows 64 bit - Accessing Attunity 32 bit drivers
  19. Importing into SQL Server 2005
  20. Business Objects Data Integrator and Attunity ODBC Issue
  21. ODBC Interface
  22. ODBC Adapter
  23. ODBC Connector
  24. Microsoft SQL server DSN configuration NT
  25. Attunity Connect SQL Query places 'Public' in front of table name in Microsoft Query
  26. HOW TO: Using the AIS ODBC Provider on UNIX
  27. SQL Server Transaction Support
  28. SQL Server Isolation Levels and Locking
  29. ODBC Supported Schema Rowsets
  30. ODBC Supported Interfaces
  31. Odbc
  32. ODBC Platforms
  33. ODBC SQLdriverCnnect
  34. ODBC with Perl
  35. Connecting from SQL DB to Attunity server using ThinODBC
  36. ERROR: DRV_Execute: DB_INF_ENGINE (1504)
  37. Studio- ERROR: acx protocol is not allowed - sacx protocol should be used
  38. HOW TO: Set the nullValue field in ADD with binary data
  39. HOW TO: bind parameter selecting records from 2 dbs with identical fields
  40. INFO: SQLExecute behavior when performing an update operation