sqlite: "library called out of sequence"
lazarus / 16-Databases

----------------------------------------------------------------------
ssamayoa · 2011-09-17 23:06

Hi.

I'm getting this error in the following situation:

Connection.Close;
Connection.DatabaseName := someFile;
Connection.Open;
SomeQuery.Open;

Connection is of type TSQLite3Connection.

Do you have suffer same problem before?

TIA.

----------------------------------------------------------------------
ssamayoa · 2011-09-19 19:54

Bump.

Any one?

BTW: Lazarus 0.9.30 / Windows 7 / Sqlite 3.7.x

----------------------------------------------------------------------
Lacak2 · 2011-09-20 10:02

Please attach some test program, which shows error ... so we can run
and test it.

----------------------------------------------------------------------
ssamayoa · 2011-09-22 15:19

Quote from: Lacak2 on September 20, 2011, 12:02:16 pmPlease attach
some test program, which shows error ... so we can run and test it.

Weird, I cant reproduce the problem in another test project.

When I can reproduce I will let you know.

Regards.

----------------------------------------------------------------------
Arbee · 2011-09-22 18:58

I've seen posts (can't remember where) that mention that this error
could be caused if you had the connection set to active at design time
as well.  Bottom line: set the connection's active property to false
in the designer and only open/close it programmatically.

----------------------------------------------------------------------
ssamayoa · 2011-09-22 22:21

Quote from: Arbee on September 22, 2011, 08:58:30 pmI've seen posts
(can't remember where) that mention that this error could be caused if
you had the connection set to active at design time as well.  Bottom
line: set the connection's active property to false in the designer
and only open/close it programmatically.

Thanks but is not the case.

Until I have some spare time I'm forcing user to close the application
if he/she wants open another "vouchers" file.

Regards.

----------------------------------------------------------------------
mch_01 · 2011-10-24 07:06

The problem is fired when you are trying to meke new connection on
closed before object (connection).
Try to comment "Connection.close". The error should disappear.