Hi all,
I'm transitioning to Delphi XE6, and moving from ADO to FireDAC. One of my projects uses many Delphi DLLs that it loads as needed at runtime. I used to pass an existing TADOConnection object from the main application to the DLL for it to use, but this doesn't seem to work with FireDAC (TFDConnection). It insists that it needs a TFDGUIxWaitCursor "added to the form", which I did (well, I created that object within the DLL), but it still insists it needs it. I've confirmed with logging that the object is definitely getting created.
My attempted fix was to pass the data source as a PChar instead (This DLL is connecting to a Microsoft Access database), and create all of the FireDAC objects within the DLL. But, it made no difference, and still insists it needs a TFDGUIxWaitCursor added to the form. BTW, while I'm testing in a VCL Forms application at the moment, once deployed, it will be within a Windows service application.
Does anyone have any experience with FireDAC that can help?
Many thanks.
I'm transitioning to Delphi XE6, and moving from ADO to FireDAC. One of my projects uses many Delphi DLLs that it loads as needed at runtime. I used to pass an existing TADOConnection object from the main application to the DLL for it to use, but this doesn't seem to work with FireDAC (TFDConnection). It insists that it needs a TFDGUIxWaitCursor "added to the form", which I did (well, I created that object within the DLL), but it still insists it needs it. I've confirmed with logging that the object is definitely getting created.
My attempted fix was to pass the data source as a PChar instead (This DLL is connecting to a Microsoft Access database), and create all of the FireDAC objects within the DLL. But, it made no difference, and still insists it needs a TFDGUIxWaitCursor added to the form. BTW, while I'm testing in a VCL Forms application at the moment, once deployed, it will be within a Windows service application.
Does anyone have any experience with FireDAC that can help?
Many thanks.