A Possible reason is you are altering metadata while connected. The
theory is you can do this, the reality is you can't. 

Allways make sure all users are disconnected before altering Meta data.

If you intend to deploy on 5.5, then I think you should get 5.5 now.
Lost connections occur a lot less with 5.5, and also some of your SQL
will change. For Example, Unions in 5.5 will return real column names as
against Pseudonyms for IB 4.2.

5.5 has it's own set of problems, but that's another problem, and I
understand an update IB5.6 is on its way to address these.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Andrew Masters
Sent: Thursday, 10 June 1999 17:21
To: Multiple recipients of list delphi
Subject: [DUG]: lost connections


Hi,

I've been developing an app with D3 and IB4.2 for some months now. In
the last week or so I have been getting an increasingly frequent error
"General SQL error, connection lost to database", but this has only just
started appearing, and in the last 6 months I've NEVER seen it. Any
clues/tips why this would be suddenly appearing. I'm using the out of
the box local IB server. It will be deployed on v5.5.

I've started writing reports with Report Printer Pro 3.0 for the last
week or so. Coincidence ?

Thanks
Andrew Masters
Clinical Solutions Ltd
Auckland, NZ
Ph: +64-9-476-0106
Fax: +64-9-476-0108 
e: [EMAIL PROTECTED]

------------------------------------------------------------------------
---
    New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
                  Website: http://www.delphi.org.nz
---------------------------------------------------------------------------
    New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
                  Website: http://www.delphi.org.nz

Reply via email to