Page 1 of 1
Strange "Connection is not defined" error
Posted: Mon 06 Jul 2015 08:01
by swierzbicki
Hello,
I'm getting an "Connection is not defined" error after setting the active property to true.
UniQuery component does have it's connection property defined (SQLite) and the database + database path exists too !
Any idea ?
Re: Strange "Connection is not defined" error
Posted: Mon 06 Jul 2015 11:42
by MaximG
We continue investigation of this issue, and we will inform you about the results shortly.
Re: Strange "Connection is not defined" error
Posted: Mon 06 Jul 2015 16:15
by swierzbicki
Please, this is really irritating...
I guess you will find this bug.
Re: Strange "Connection is not defined" error
Posted: Thu 09 Jul 2015 13:44
by MaximG
Investigation of this problem showed, that the error occurs either due to module loading disorder or due to early call of the TComponent.Loaded method - before the Connection of the Query is set, which leads to «Connection is not defined». The problem is reproduced on all the standard data access components. We have posted the bug description to Embarcadero:
https://quality.embarcadero.com/browse/RSP-11440 . A temporary workaround is to place the components in one Data Module.
Re: Strange "Connection is not defined" error
Posted: Fri 10 Jul 2015 08:18
by swierzbicki
Thank you for the feedback.
I'll move all unidac components to the datamodule.