On Tue, 3 Jul 2007, Arí Ricardo Ody wrote:
> I've wrote a single application that connects with a Firebird database in a > server in a windows XP network. From an initial form I go to another that only > open a DBGRID and user can navigate forward and backward in a single browse or > go to another form where the user can inform a search argument and the program > executes a SELECT in the Firebird database and shows the result in a DBGRID. > > Well, while I navigate from the first form to any one of the other two and > back to the first everything's run ok. > > When the user click in the exit button of the first form a execute the > "Self.Close" method and the application/program freezes. The trouble seems to > be that the program have troubles to disconnect from the remote server. If I > run the same application in a local database no troubles occur. IMHO, the problem is not in Lazarus, but in Firebird. The lazarus code does not care or even does not know where the firebird database is: The code for this is 100% the same. It is the gds32.dll (or fbclient.dll) code which is responsible for handling the close() call. The gds32.dll library (or fbclient.dll) decides that the database is remote if the database name is prepended with the hostname. That is all. If you connect to the database with some other too, e.g. flamerobin, you should experience the same problem. Michael.
