VB6 is the original Visual Basic, unfortunately ditched by MS some years ago and replaced by .Net.
Yes, I am sure it is some kind of memory problem, but where (what line) could it possibly occur? All I can think of is this line: sqlite3_result_text lPtr_ObjContext, VarPtr(arrBytes1(0)), lPos - 1, SQLITE_TRANSIENT But as it uses SQLITE_TRANSIENT, I understand SQLite will make local copy and deal with it properly itself. All the other code is just copying data from SQLite to local VB6 variables. RBS On Sat, Dec 26, 2015 at 6:52 PM, Simon Slavin <slavins at bigfraud.org> wrote: > > On 26 Dec 2015, at 5:23pm, Bart Smissaert <bart.smissaert at gmail.com> > wrote: > > >> all is perfectly fine when the SQL statement has only one UDF in it > > > > Just a correction on this. Have now also seen problems when there is only > > one UDF in the SQL statement. > > It is not entirely predictable, so sometimes get crash and on other > > occasions I don't. > > That is typical of memory mis-management problems everyone runs into from > time to time. You are probably releasing or overwriting memory which > SQLite thinks it can depend on. Unfortunately I don't know the version of > BASIC you're using, but your commands 'ReDim', for example, make me think > memory is being released. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users at mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users >
