Ron Schuster

Our C# .NET team creates Managed Code DLLs for us to call from our Delphi desktop application. They call them "COM-wrapped .NET". We use Regasm.exe (Assembly Registration Tool) to register the Managed Code DLLs. We they are registered I can see them in the Windows registry. Now I have a new one of these and no one can remember how we got these imported into Delphi. We have *_TLB.PAS files for the old ones, so we apparently successfully imported these in Delphi. I expected to go into Component -> Import Component -> Import a Type Library, find it in the list of Registered Type Libraries, and go from there, but none of these show up in the list. They also produced a .TLB file to go with the .DLL, and I can successfully open this file directly (File -> Open) in Delphi and view the classes with all their methods and parameters, but I can't do anything with it from there. What do I need to do to import these .DLLs?

Angus, As I stated in my original post, it does not appear there. That is the main point of my issue.

Is there a way to find out what driver (ODBC, SQL Native Client, etc. ) that FireDAC is actually using when establishing a connection to the MSSQL database? In the FireDAC connection all we get to specify is DriverID = MSSQL and FireDAC apparently chooses an appropriate driver based on what's available.

What would be the reason that I would want to assign a driver other than one FireDAC chooses by default?