> I've seen a few issues myself, but they all appeared to be related to > the memory management thing. If you're using VC, try putting this into > your code:
Thanks to you both for answer. However, I using BCC55 currently (Borland's free commanlinetools compiler v.5.5.1). And I've had publich on my site all what is needed to be compiled with it. And regarding linking Delphi, I created stub of most used C functions which can be supported easy with Delphi code, as they are memory functions, some conversions, working with strings...). That is the reason it can be used any MM used in application, instead of supplied with C/C++. With Delphi applications I usually using FastMM4 (Fastcode Memory Manager version 4.xx). It is much faster than original Borland's MM and actually it is replaced by Borland itself starting from Delphi2005. It also have functions to report leaks when program closing/exit. Regarding Cristian's answer, I do releasing ErrMsg with sqlite3_free(ErrMsg) at the end of program. And that seems to be a problem according to SQLite code: for initializing error messages pointer is simms to always using malloc. That force releasing error messages pointer after each function which using it. Using realloc instead (when pointer is non NIL) may solve the problem. Sasa -- www.szutils.net
