I'm fairly confused. But if you changed the way vec handles look "The redesign was to get rid of that ugly global table and use dynamically allocated vector structures; the vector handle is now the address of the handle (with 00's escaped)."
there's definitely gonna be problems, unless you changed my code for vec_exists(pszArg). (odbc/sqlite don't need to call that: they _know_ a specific parameter is gonna be a handle to a vec, no debate. Regex code replies on inspecting a particular parameter to see if it's a vec handle or not, and acting accordingly). In another post you said source code was included with something. I downloaded a vec dll, not enclosed in a zip. Source code is where? --- In [email protected], "Sheri" <sheri...@...> wrote: > > --- In [email protected], "brucexs" <brucexs@> wrote: > > > > > > > Replacing vec is all that is required for my stuff to work again. > > > How old is this vecold? I was previously up and running with a > > > recent test version. > > > > By recent test version, do you mean the one from a couple of days > > ago or the one from last week? > > Pretty sure a couple days ago. > > I tried the one you released again. Here is another error message. I guess > regex must be using vec internally, maybe service parameters are in a vector. > > --------------------------- > PowerPro > --------------------------- > ERROR: regex.pcreReplace: Bad input params > > Error occurred near line 114 of script regexembede: > local mykeymenu1=regex.pcrereplace(?"(?s)\r\nsep\r\n", mykeymenu1, > "\r\n[1]\r\nLCmd1 = *Format\r\nLParam1 = Separator\r\nMCmd1 = (none)\r\nRCmd1 > = (none)\r\n\r\n", "literal") > > Press Cancel to end all running scripts. > --------------------------- > OK Cancel > --------------------------- > > Regards, > Sheri >
