> What is this btLBAdd that you have in one place but not the other? To avoid confusion I took the correction factor out of the first code line, but not the second. My fault. This correction factor is to accommodate both 0-based and 1-based arrays (VB6 can do that). This is not the problem.
I think I am on the right track now. I checked the bound values after binding a whole row, but should check after every value and can see now where it goes wrong. Sure this will be fixed soon now and indeed nil to do with SQLite. RBS On Fri, Jan 20, 2017 at 11:33 PM, Igor Tandetnik <i...@tandetnik.org> wrote: > On 1/20/2017 6:15 PM, Bart Smissaert wrote: > >> Good idea, >> I have checked for this but will double check again. >> The problem arises already with the very first element of the variant >> array >> and my log shows the problem: >> >> logged before the bind: >> vArray(0, 0): 1 >> > > Wait, you are indexing from 0? sqlite3_bind_int numbers parameters > starting from 1. What is this btLBAdd that you have in one place but not > the other? > > Also, as a sanity check, print CType() of that element and, if it's a > string, the length of that string. > > -- > Igor Tandetnik > > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
