Hello,

I just installed a Xbase 2.0 with L&L 21 on a windows 2008 server.
The same app ran before on the same server wirh L&L19 and Xbase++ 1.9
In windows 7 and 10 there is no problem with this same programm in 2.0 and L&L21

Now  i get a runtime errer on FUNCTION LlDefineVariableExt( hLlJob,pszVarName, lpbufContents,lPara,lpPtr)
In 2 differen applicaions, on exactly the same point.
It fails on the verry first call of this function LlDefineVariableExt.

oError:args :
P1 = VALTYPE: C VALUE: _DLL  mÐrOm  ð
P2 = VALTYPE: N VALUE: 1
P3 = VALTYPE: C VALUE: Systeem.Afdrukdatum
P4 = VALTYPE: C VALUE: 05-10-2016
P5 = VALTYPE: N VALUE: 268435456
P6 = VALTYPE: N VALUE: 0
oError:canDefault :.F.
oError:canRetry :.F.
oError:canSubstitute:.T.
oError:cargo :NIL
oError:description :Internal data structures corrupted 
oError:genCode :41 
oError:filename :
oError:operation :dllExecuteCall
oError:osCode :0
oError:severity :2
oError:subCode :5
oError:subSystem :BASE
oError:thread :7
oError:tries :0



 Below the code as generated by compiling LL21\Programmable Samples and Declarations\Alaska Xbase++\cmbtll21.prg

FUNCTION LlDefineVariableExt( hLlJob,pszVarName, lpbufContents,lPara,lpPtr)
STATIC cTemplate := NIL
LOCAL xRet 
IF hDll == 0	
    RETURN(NIL)
ENDIF
IF cTemplate==NIL
    cTemplate := DllPrepareCall( hDll, 32, 23 )
ENDIF 
xRet := DllExecuteCall(cTemplate, hLlJob,@pszVarName,@lpbufContents,lPara,lpPtr)
RETURN xRet





Regards
Jack Duijf

-------------------------------------------------------------
Also a member off the XXP (http://www.xxp.nl)

Jack,

>I just installed a Xbase 2.0 with L&L 21 on a windows 2008 server.
>The same app ran before on the same server wirh L&L19 and Xbase++ 1.9

The type of runtime error (IDSC) and the circumstances that you describe, 
would make me suspect a DLL version mismatch problem. As both versions of 
Xbase++ and both versions of L&L apparently work together on other machines, 
and because the problem computer had (apparently) previously older versions 
of both Xbase++ and L&L installed on it, I suspect that some DLLs of one (or 
both) programs remain somewhere in the path.

You could use XppLoad.exe to check the DLL versions or even better, use 
Dependency Walker to determine which DLL files are actually loaded by your 
application.

Hope that helps,

Andreas

Andreas Gehrs-Pahl
Absolute Software, LLC

phone: (989) 723-9927
email: Andreas@AbsoluteSoftwareLLC.com
web:   http://www.AbsoluteSoftwareLLC.com
[F]:   https://www.facebook.com/AbsoluteSoftwareLLC