Alaska Software Inc. - DLL issues / LineSplit
Username: Password:
AuthorTopic: DLL issues / LineSplit
Jeff GillardDLL issues / LineSplit
on Tue, 30 Dec 2014 15:59:49 -0500
Hello,

We recently installed 2.0 using a side by side install.  I brought in one of 
my XPJ files and was able to get it compiling properly but when I went to 
run it I got the error below.  I moved the DLL files from the C:\Program 
Files\Alaska Software\xpp20\lib\ to the directory that my 2.0 executable is 
in but still get this message.  How do I resolve this?

The procedure entry point __This_DLL_Needs_version_1_90_0 could not be 
located in the dynamic link library XPPRT1.DLL.

Also - I had to comment out a call to a function named LineSplit saying it 
was an unresolved external symbol.  I can't recally where this function came 
from or why it's not linking - any ideas?
Peter AlderliestenRe: DLL issues / LineSplit
on Fri, 02 Jan 2015 13:44:57 +0100
Jeff,

> ... I moved the DLL files from the C:\Program 
> Files\Alaska Software\xpp20\lib\ to the directory that my 2.0 executable is 
> in but still get this message.  How do I resolve this?

I hope you mean  .. copied the DLLs
There's no need to mess with the Xbase++ installation for a side by side
install. There are neater ways to handle that.

> The procedure entry point __This_DLL_Needs_version_1_90_0 could not be 
> located in the dynamic link library XPPRT1.DLL.

This message shows that there libraries/DLLs used (Express++ / TopDown?)
that are still created with 1.90

> Also - I had to comment out a call to a function named LineSplit saying it 
> was an unresolved external symbol.  I can't recally where this function came 
> from or why it's not linking - any ideas?

I have seen a function like this to read data into an array in one of the
Xbase++ samples.

Peter
Jeff GillardRe: DLL issues / LineSplit
on Fri, 02 Jan 2015 12:23:28 -0500
Peter,

Yes - I meant that I copied, not moved.  I have since removed these DLLs 
from the directory my executable is running in and have setup my environment 
options in the Workbench to remove any references to the 1.9 paths.

I have the following 3rd party DLL files which are stored in a separate 
directory and setup as an executable path from the workbench environment 
options:

XBPCRE.DLL
BAP2.DLL
OT4XB.DLL
RECPP.DLL
XB2NET.DLL

To the best of my knowledge, only XB2NET.DLL needed to be updated to the 
xbase 2.0 version and I have downloaded it from xb2.net.



<Peter Alderliesten> wrote in message 
news:1hatrioxfrstk$.1nmcysy4hhiix.dlg@40tude.net...
> Jeff,
>
>> ... I moved the DLL files from the C:\Program
>> Files\Alaska Software\xpp20\lib\ to the directory that my 2.0 executable 
>> is
>> in but still get this message.  How do I resolve this?
>
> I hope you mean  .. copied the DLLs
> There's no need to mess with the Xbase++ installation for a side by side
> install. There are neater ways to handle that.
>
>> The procedure entry point __This_DLL_Needs_version_1_90_0 could not be
>> located in the dynamic link library XPPRT1.DLL.
>
> This message shows that there libraries/DLLs used (Express++ / TopDown?)
> that are still created with 1.90
>
>> Also - I had to comment out a call to a function named LineSplit saying 
>> it
>> was an unresolved external symbol.  I can't recally where this function 
>> came
>> from or why it's not linking - any ideas?
>
> I have seen a function like this to read data into an array in one of the
> Xbase++ samples.
>
> Peter
Andreas HerdtRe: DLL issues / LineSplit
on Mon, 05 Jan 2015 15:00:06 +0100
Jeff, Peter,

Happy New Year 2015.

The function LineSplit is a helper function in errorsys.prg. In previous
Xbase++ versions this function was exported in xppsys.dll.

With version 2.0 the function is declared STATIC because of consistensy
and because it is not intended to be officially supported.

If your code utilizes LineSplit() then simply copy the source from 
<documents>\Xbase++\source\runtime\errorsys.prg and add this
function to one of your prg files.

With my best regards,

  Andreas Herdt
  Alaska Software

--------------------------------------------------------------------

Technical Support:      support@alaska-software.com

News Server:            news.alaska-software.com
Homepage:               http://www.alaska-software.com
WebKnowledgeBase:       http://www.alaska-software.com/kbase.shtm

Fax European Office:    +49 (0) 61 96 - 77 99 99 23
Fax US Office:          +1 (646) 218 1281
--------------------------------------------------------------------

"Peter Alderliesten" wrote in message 
news:1hatrioxfrstk$.1nmcysy4hhiix.dlg@40tude.net...
> Jeff,
>
>> ... I moved the DLL files from the C:\Program
>> Files\Alaska Software\xpp20\lib\ to the directory that my 2.0 executable 
>> is
>> in but still get this message.  How do I resolve this?
>
> I hope you mean  .. copied the DLLs
> There's no need to mess with the Xbase++ installation for a side by side
> install. There are neater ways to handle that.
>
>> The procedure entry point __This_DLL_Needs_version_1_90_0 could not be
>> located in the dynamic link library XPPRT1.DLL.
>
> This message shows that there libraries/DLLs used (Express++ / TopDown?)
> that are still created with 1.90
>
>> Also - I had to comment out a call to a function named LineSplit saying 
>> it
>> was an unresolved external symbol.  I can't recally where this function 
>> came
>> from or why it's not linking - any ideas?
>
> I have seen a function like this to read data into an array in one of the
> Xbase++ samples.
>
> Peter
Jeff GillardRe: DLL issues / LineSplit
on Thu, 08 Jan 2015 21:32:40 -0500
Andreas,

Thanks for the info - I'll check into that.

As for the DLL issue, it ended up being our use of XBPCRE.DLL that was 
compiled under 1.9SL1.

Salar

<Andreas Herdt> wrote in message 
news:748f435a$8d639$129a@news.alaska-software.com...
> Jeff, Peter,
>
> Happy New Year 2015.
>
> The function LineSplit is a helper function in errorsys.prg. In previous
> Xbase++ versions this function was exported in xppsys.dll.
>
> With version 2.0 the function is declared STATIC because of consistensy
> and because it is not intended to be officially supported.
>
> If your code utilizes LineSplit() then simply copy the source from 
> <documents>\Xbase++\source\runtime\errorsys.prg and add this
> function to one of your prg files.
>
> With my best regards,
>
> -- 
>  Andreas Herdt
>  Alaska Software
>
> --------------------------------------------------------------------
>
> Technical Support:      support@alaska-software.com
>
> News Server:            news.alaska-software.com
> Homepage:               http://www.alaska-software.com
> WebKnowledgeBase:       http://www.alaska-software.com/kbase.shtm
>
> Fax European Office:    +49 (0) 61 96 - 77 99 99 23
> Fax US Office:          +1 (646) 218 1281
> --------------------------------------------------------------------
>
> "Peter Alderliesten" wrote in message 
> news:1hatrioxfrstk$.1nmcysy4hhiix.dlg@40tude.net...
>> Jeff,
>>
>>> ... I moved the DLL files from the C:\Program
>>> Files\Alaska Software\xpp20\lib\ to the directory that my 2.0 executable 
>>> is
>>> in but still get this message.  How do I resolve this?
>>
>> I hope you mean  .. copied the DLLs
>> There's no need to mess with the Xbase++ installation for a side by side
>> install. There are neater ways to handle that.
>>
>>> The procedure entry point __This_DLL_Needs_version_1_90_0 could not be
>>> located in the dynamic link library XPPRT1.DLL.
>>
>> This message shows that there libraries/DLLs used (Express++ / TopDown?)
>> that are still created with 1.90
>>
>>> Also - I had to comment out a call to a function named LineSplit saying 
>>> it
>>> was an unresolved external symbol.  I can't recally where this function 
>>> came
>>> from or why it's not linking - any ideas?
>>
>> I have seen a function like this to read data into an array in one of the
>> Xbase++ samples.
>>
>> Peter
>