Relativity and ODBC connections

New to Relativity and not finding documentation on all the various dll files and drivers. Can anyone give me a listing of the various dll files and drivers and how they are using them?  From what I have obtained so far the Data Manager driver would be used by Designer for DSN access to the catalog, but you are also able to select the Data Client, Data Client for ADO, Relativity DBA, and Data Server in the Designer product. If I understand correctly the Data Client for ADO is used in SQL linked servers and also for other Visual Studio projects that need to access the Cobol data. Is that correct and what about the other drivers? Also I am working with another developer to have connection strings into the catalog - since I set up the DSN using the Data Client for ADO does that mean they need to use one of the dll files under Relativity Data Client folder?  All replies appreciated.

This is what I see and I just need direction is what to share with my developer that is relavant.

Relativity Designer driver with the following dll files - obviously some of them are internal for compiling and creating the file layouts

  KenlyGenProcessor.dll

  kenlygenprocessor222.dll

  RelCblAst.dll

 relhp32.dll

  relimporter.dll

  relutl32.dll

  Rstlmp.dll

  ssubtmr6.dll

  tdbgpp.dll

  Relativity Data Client with the following dll files

   relADC32.dll

  relcln32.dll

  relcs32m.dll

  relfmf32.dll

  relink32.dll

Relativity Data Manager with the following dll files

  reldbm32.dll

  relfmf32.dll

  relstp32.dll

Relativity Data Server with the following dll files

  reldbmsg.dll

  reldbsrv.dll

  relfmf32.dll

  relstp32.dll

Relativity DBA with the following dll files

  relhlp32.dll

  relutl32.dll

  tdbgpp.dll

Parents
  • <<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.)

Reply
  • <<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.)

Children
No Data