A previous ODBC connector that we use required the use of a certain dll when doing connections from Visual Studio solutions and that was the main thing my co-worker was asking about. Hmmm. I have no idea what the "previous ODBC connector" did, but with ODBC, you just establish the connection using the Data Source Name used with the data source was created. The ODBC driver manager takes care of loading the correct DLL. It would appear that the previous solution encountered the same issues with ADO that Relativity did, and they solved it with a separate DLL. Relativity also has a separate DLL for ADO access, but it is associated with the "for ADO" drivers. So, to be clear, the same Relativity catalog may be used with both a Relativity Data Manager driver and a Relativity Data Manager for ADO driver. I'm not sure about the performance of doing this, so I would not recommend using that in a production environment. (Just make a copy the developed catalog and create the separate ADO data source to the copy of the catalog.)
↧