LoginPromt in OnBeforeConnect with TfrxLiteDACComponents

Discussion of open issues, suggestions and bugs regarding LiteDAC (SQLite Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
LHSoft
Posts: 104
Joined: Sat 18 Aug 2012 08:33

LoginPromt in OnBeforeConnect with TfrxLiteDACComponents

Post by LHSoft » Wed 31 May 2017 13:35

Hello,
got a strange behavior again:
In OnBeforeConnect of LiteConnection I write

Code: Select all

LiteConnection.LoginPrompt := False;
This works perfect unless I add a TfrxLiteDACComponents somewhere in the project (only the unit frxLiteDACComponents, other frx do not matter).
If so, the LoginPrompt appears before the OnBeforeConnect is triggered.

I can avoid this by setting the LiteConnection on the Form to LoginPromt = False, so it is no big problem. In spite it would be fine if there is the same behavior with and without frxLiteDACComponents on project.

best regards
Hans

MaximG
Devart Team
Posts: 1094
Joined: Mon 06 Jul 2015 11:34

Re: LoginPromt in OnBeforeConnect with TfrxLiteDACComponents

Post by MaximG » Fri 02 Jun 2017 13:53

Thank you for the information. We have reproduced the issue and will investigate its origin. We will inform you about the results shortly.

LHSoft
Posts: 104
Joined: Sat 18 Aug 2012 08:33

Re: LoginPromt in OnBeforeConnect with TfrxLiteDACComponents

Post by LHSoft » Sun 15 Apr 2018 13:09

Hello,
I want to remeber that this is still not solved.
best regards
hans

MaximG
Devart Team
Posts: 1094
Joined: Mon 06 Jul 2015 11:34

Re: LoginPromt in OnBeforeConnect with TfrxLiteDACComponents

Post by MaximG » Tue 10 Jul 2018 08:37

This behavior is a specificity of our components implementation and at present, as a workaround, you can set the LoginPromt connection option to False. We will consider a possibility of changing the behavior in the way you are describing in one of the next versions of our product

MaximG
Devart Team
Posts: 1094
Joined: Mon 06 Jul 2015 11:34

Re: LoginPromt in OnBeforeConnect with TfrxLiteDACComponents

Post by MaximG » Wed 12 Sep 2018 15:16

We have reproduced the problem and fixed the bug. The fix will be included in the next LiteDAC build.

Post Reply