I should close this problem created by myself. It was due to having comments &&
after DLL function declaration.

Declare something1 in "something2" && bla-bla
DECLARE STRING GetResult IN "XPRConnector.dll"

creates this side effect.

>It is nothing to do with parameterless functions. Declaration is just ignored if we issue "DISPLAY STATUS"
>
>Declared DLLs:
>CasbahConnect d:\tt4dev\xprconnector.dll
>GetActiveWindow C:\WINNT\system32\USER32.dll
>SetXPRRequestValues d:\tt4dev\xprconnector.dll
>
>I've got DLL source code either but function definition doesn't seem to be very helpful to explain the problem.
>
>PSTR GetResult()
>{
> return response.GetBuffer(0);
>}
>
>
>>I have a problem indirectly related to Windows API but might be relevant for function calls without parameters.
>>
>>DECLARE STRING GetResult IN "XPRConnector.dll"
>>
>>string = GetResult()
>>
>>gives an error
>>
>>"file getresult.prg does not exist"
>>
>>though two other function calls with parameters for the same DLL didn't result in similar error.
>>
>>No problem in VB with that
>>
>>Private Declare Function GetResult Lib "XPRConnector.dll" () As String
>>Text1.Text = GetResult()
>>
>>Any clues ?
>>
>>Thank you.
>>Michael