"Bart Smissaert" <bart.smissa...@gmail.com> schrieb im Newsbeitrag news:aanlktil5lha-3-l6x8umwv8e3pyrda6h0ln3dcoyh...@mail.gmail.com...
> Yes, it must be either my code or the wrapper to blame. > Thanks for confirming. It's a wrapper-"problem", but a perhaps a coding problem as well... ;-) The wrapper overrides sqlites internal Like-Function, to achieve (Unicode-)BSTR mapping. Internally VBs normal Like-Function then does "all the rest". The wrapper (due to compatibility reasons with regards to JET *.mdbs) also understands their older "like-syntax": "...Where SomeColumnContent Like '*somepart*' (in this regards behaving somewhat similar to SQLites glob, which BTW was _not_ overriden)... But it supports the "default-like-syntax" as well: "...Where SomeColumnContent Like '%somepart%' To specify single chars, which are equal to the "comparison- descriptors" you have to "escape them" within brackets: "...Where SomeColumnContent Like '%someother[*]part%' If the above should not work, then this would be considered a "real wrapper-bug". ;-) HTH Olaf Schmidt _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
