FiveTech Software tech support forums

Antonio, Originally I used the samples' libraries, but when the Unresolved externals started to popup, I used XSearch utility to look for the function names inside *.LIB files. More than 1 files are listed so I picked those filenames that come from the folders: 1) harbour 2) fwh1304 3) bcc582 Until ...

Anybody, I tried comverting our codes to Harbour/FWH1304. After trials and misses especially when choosing the right LIB files during a search for Unresolved externals, I finally made it through to build the EXE. But when run, either XHB-32-BCC.DLL and/or HARBOUR-32-BCC.DLL are not found. I searched...

anybody, what's wrong in the code below? #include "FiveWin.ch" #include "colors.ch" //----------------------------------------------------------------------------// function Main() STATIC isOn := .F. STATIC oDlgWt, nWidth, oFont14 Local oMsg, nHeight, nMsgWidth, nDlgWidth DEFAULT...

FWH13.04 / xHarbour Commercial 2009 works, at least for some samples.

Toyet

Antonio,

My apologies, looks like these functions don't belong to fivewin.

Toyet

Antonio, when i compiled a running program with FWH1304/xHarbour/xCC, IsZip() and also the other ZIP functions were rendered Unresolved Externals, xLINK: error: Unresolved external symbol '_HB_FUN_ISZIP referenced from (licmanag.obj)'. xLINK: error: Unresolved external symbol '_HB_FUN_GETFIRSTINZIP ...

thats why it seems to me that xharbour is not interested in 64 bits, same as it is not interested in OSes different from Windows, and this is unacceptable to me

good point here Antonio!

Toyet

Tim,

Have you tried FWH64 with xHarbour?

Toyet

GN Rao,

I tried the Ceiling() function and it seems to go fine. Thank you for it.

Maybe the '%' operator for modulus division is the culprit for the error?

Toyet

Any ideas why the red line below produces a syntax error at '(' nEmployeeMax := 33 nEmployeeCount := 0 nPageE := int(nEmployees/nEmployeeMax) + if(nEmployees % nEmployeeMax > 0, 1, 0 ) nPageC := 0 Fivewin 13.04 / Harbour 3.2.0 (rev 18881) Thanks for any help. Toyet

Antonio, The very looong list of unresolved externals is now reduced to: xLINK: error: Unresolved external symbol '_SendInput referenced from FiveHCM.lib(KEYBRD.obj)'. xLINK: error: Unresolved external symbol '_GlobalMemoryStatusEx referenced from FiveHCM.lib(MEM.obj)'. xLINK: error: Unresolved exte...

Thanks, Antonio. Many Thanks.

I'll let you know the results later.

Toyet

Antonio, Well, every penny that we save is a penny earned you know. :) Our second option is to use the Harbour that comes with FWH. Anyway, is there really no other way? The errors seems to come mostly from FiveHCM.lib. Here's the last of the long list of unresolved externals: xLINK: error: Unresolv...

Antonio,

I remember sometime ago when we use different versions of xharbour and fivewin, there was an XBP file posted somewhere and we just rebuild the FiveHMX.lib to the xHarbour version of interest.

Am thinking if this is the same case.

Toyet

Is there something we must do to be able to build FIVEWIN 13.04 using xHarbour November 2009?
We seem to have error(s). Thanks in advance.
Toyet