Sasha,

> i make run-time packages..

Two things...

1. Be careful about how objects are constructed via DLL and BPLs.
Make sure they are always owned and instantiated by the application
itself so that they will be destroyed in the correct order. (Either
that or be sure to write your library/dll to take care of these issues
itself.)

It is usually simplest to have the TIB_Connection and/or database
components as part of the application and link DLL classes to these
objects when they are instantiated. Of course it all depends on what
you want to achieve, I am simply saying this is the simplest way to
manage things without having to write too much code.


2. You may find it interesting to compare the memory useage of your
application between using runtime packages and using all-in-one
executables.

A current version of one of my appliations uses runtime packages and
consumes 15Mb at startup. The same application compiled as all-in-one
uses 7Mb!!! I am told this is a known problem with runtime packages
and may or may not be important to you. Since my application is
running of terminal server (lots of users running on the same machine)
it was an important discovery for me.

HTH

Geoff Worboys
Telesis Computing