Hello
I have replacement procedure for errorsys, dbesys and getsys linked in a 
common DLL. Until VX I have no problem with this, but now the linker use 
either my own procedure from my DLL or the standard procedure for Alaska 
DLL depending the project. I can't see why. Is there a way to force 
linker to use my procedure.
Regards

  Christian Laborde
GTS Gestion-Technologie-Services

Route de la Corniche, 1
CH 1096 Cully
Suisse

> I have replacement procedure for errorsys, dbesys and getsys linked in a
> common DLL. Until VX I have no problem with this, but now the linker use
> either my own procedure from my DLL or the standard procedure for Alaska
> DLL depending the project. I can't see why. Is there a way to force
> linker to use my procedure.

Christian,

normally, this only occurs if you aren't linking the DLL into your project.
Be sure to add a "#pragma LIBRARY()" statement into your code.

Regards,
  Till

  [Alaska Research & Development]

Hello
This happens since I remove the DLL from my project and add the pragma.
I send you two projects and corresponding log (verbose). You can see the 
different way getsys and errorsys are linked.
Regards.

  Christian Laborde
GTS Gestion-Technologie-Services

Route de la Corniche, 1
CH 1096 Cully
Suisse

"Christian Laborde" <infolab@bluewin.ch> wrote in message
news:86Zh#Yk6DHA.2016@S15147418...
> Hello
> This happens since I remove the DLL from my project and add the pragma.
> I send you two projects and corresponding log (verbose). You can see the
> different way getsys and errorsys are linked.

Christian,

thanks for the files. We'll have a look at them.

Regards,
  Till Warweg

--
---------------------------------------------------
ARD - Alaska Research & Development

Web:       http://www.alaska-research.com
Investors: http://www.alaska-research.com/tifund
E-Mail:    mailto:till.warweg@alaska-research.com
Contact:   mailto:info@alaska-research.com
---------------------------------------------------

Christian Laborde wrote:
> Hello
> This happens since I remove the DLL from my project and add the pragma.
> I send you two projects and corresponding log (verbose). You can see the 
> different way getsys and errorsys are linked.
> Regards.

Hi Christian,

Please find attached a tiny Project with three targets:

    1. an executable that calls standard errorsys
    2. an executable that calls the overloaded errorsys
       ( sys.lib is included with #pragma Library )
    3. a library that implements the errorsys
       ( basically this is a copy of the default errorsys )

Please try both exes at your side and report:

1. Do they work as expected?
2. If not, what are the differences between the pattern here
    and the pattern you are using?

Regards
   Andreas Herdt
   [Alaska Research & Development]

No attachment !
Regards

  Christian Laborde
GTS Gestion-Technologie-Services

Route de la Corniche, 1
CH 1096 Cully
Suisse

Christian Laborde wrote:
> No attachment !
> Regards

Regards
   Andreas Herdt
   [Alaska Research & Development]

Hey
The problem comes from sorting. Modules are processed in alphabetic 
order. Well linked project start with module ABX000, other start with 
module ARC000. If I add a pragma for my lib in the module ADR000, Link 
is well done in the second project.
Look at this.
Regards.

Christian Laborde
GTS Gestion-Technologie-Services
True E-mail : remove dash and no spam
Route de la Corniche, 1
CH 1096 Cully
Suisse