If you are using PBDs, be sure the PBD containing this object is in your
application library.
If you are not using PBDs, be sure the NVO name is listed in the resource
file.
Assuming the above are true, delete all your PBDs and EXE and recreate
application, use brand new PBDs/EXE created at same time. Be sure "Full
Rebuild" and not "Incremental" is selected when you do the build.
In my experience, the PBL order has little affect, but for what it's worth,
I do APP PBLS, PFE, PFC.
----- Original Message -----
From: Crompton, Vivian (London) <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 17, 1999 1:43 PM
Subject: PFCSIG "Unresolvable external" at Run time, no error at design
time.
> Hi All,
> I have a PFC based app that is stubbornly refusing to work when I build an
> executable.
> I am getting the following:
> Unresolvable external n_cst_dwtotext when linking reference
>
> The error only occurs at run time, after an event that uses the object is
> fired.
> At design time ( ie. within the powerbuilder development environment) the
> application runs perfectly, whether running it or stepping through the
code
> in the debugger.
>
> I have tried the usual tricks of reegnerations, complete rebuilds,
exporting
> the object and reimporting it, etc. and have also restarted NT, done all
of
> the above again, to no avail.
> Any suggestions as to the cause of this kind of error? It's driving me
nuts.
>
> Thanks,
>
> Vivian
>
>
> > [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS,
ADDRESS
> > A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help
pfcsig
> > SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
>
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
