A way to avoid an access violation at <SQLQuery>.Active:= true
Original Reporter info from Mantis: vano
-
Reporter name: IvankoB
Original Reporter info from Mantis: vano
- Reporter name: IvankoB
Description:
&LtPos;SQLConnection> - &LtPos;PQConnection> from the SQLDB package.
The steps:
- &LtPos;SQLConnection> de dropped and tuned so that Active:= true is Ok;
- &LtPos;SQLTransaction> be dropped on the form;
- &LtPos;SQLConnection>.Transaction be set to the above &LtPos;SQLTransaction>;
- &LtPos;SQLQuery>.Database be set to &LtPos;SQLConnection> and automatically &LtPos;SQLQuery>.Transaction:= &LtPos;SQLTransaction>
Failing to do steps 2) and 3) leads to AV at &LtPos;SQLQuery>.Active:= true.
Why not to block &LtPos;SQLQuery>.Active:= true until the necessary steps are checked ? Or it can only be resolved in FCL(SqlDb)?
Mantis conversion info:
- Mantis ID: 1721
- OS: Linux
- OS Build: Debian sarge
- Platform: i386
- Version: 0.9.13 (SVN)
- Fixed in revision: fpc 2662 (#8ab6a60b)
- Target version: post 1.0