nageswaragunupudi wrote:We had this problem with some versions of xharbour.
I am using xHarbour Compiler build 1.2.1 (SimpLex) (Rev. 9381)
This is the build provided by FiveWin.
This version is working well.
You may try this version, instead of going back to an older version.
nageswaragunupudi wrote:http://forums.fivetechsupport.com/viewtopic.php?f=17&t=21875
We need to build our own rddads
function FWGetOleObject( cApp )
local oObj
TRY
oObj := TOleAuto():New( cApp )
CATCH
END
return oObj
ShumingWang wrote:Yes, on some win7 with problems.for example: excelObj() vs oExcel := GetOleObject( "Excel.Application" ) calls toleauto() class,but harbour 3.0 comes better win_oleauto class, I do not find the source file getoleobject() to replace it win_oleauto class.
Regards!
Shuming Wang
nageswaragunupudi wrote:ShumingWang wrote:Yes, on some win7 with problems.for example: excelObj() vs oExcel := GetOleObject( "Excel.Application" ) calls toleauto() class,but harbour 3.0 comes better win_oleauto class, I do not find the source file getoleobject() to replace it win_oleauto class.
Regards!
Shuming Wang
May I know which version of FWH are you using?
Please change the function name GetOleObject in olefuncs.prg as FWGetOleObject and in all its references.
GetOleObject name in olefuncs.prg was clashing with function of the same name in xHarbour
function ExcelObj()
static lInstalled
static oExcel
if !( lInstalled == .f. )
lInstalled := ( ( oExcel := FWGetOleObject( "Excel.Application" ) ) != nil )
endif
return oExcel
function FWGetOleObject( cApp )
local oObj
TRY
oObj := TOleAuto():New( cApp ) //from GetActiveObject( cApp )
CATCH
TRY
oObj := TOleAuto():New( cApp )
CATCH
END
END
return oObj
Return to FiveWin for Harbour/xHarbour
Users browsing this forum: nageswaragunupudi and 77 guests