FiveTech Software tech support forums

... build Harbour yourself or do you prefer me to send it to you ? For what C compiler ?

The fix:
in harbour/contrib/hbwin/olecore.c

HB_FUNC( WIN_OLEAUTO___ONERROR )
...
if ((HB_ISBYREF(1)) || HB_ISARRAY(1))
lOleError = HB_VTBL( pDisp )->Invoke( HB_THIS_( pDisp ) dispid, HB_ID_REF( IID_NULL ...

... BOF EOF
1 1 .F. .F.

Indexes in use TagName

Relations in use

Classes in use:
===============
1 ERROR
2 HBCLASS
3 HBOBJECT
4 TFONT
5 WIN_OLEAUTO
6 TOLEAUTO
7 TWINDOW
8 TDIALOG
9 TBRUSH
10 TCONTROL
11 TICON
12 TMULTIGET
13 TBUTTON
14 TRECT
15 TSAY
16 TGET
17 GET
18 TCLIPGET
19 ...

... BOF EOF
1 1 .F. .F.

Indexes in use TagName

Relations in use

Classes in use:
===============
1 ERROR
2 HBCLASS
3 HBOBJECT
4 TFONT
5 WIN_OLEAUTO
6 TOLEAUTO
7 TWINDOW
8 TDIALOG
9 TBRUSH
10 TCONTROL
11 TICON
12 TMULTIGET
13 TBUTTON
14 TRECT
15 TSAY
16 TGET
17 GET
18 TCLIPGET
19 ...

Does anyone know where I can find TOLEAUTO.PRG source file?

xHarbour:
source\rtl\win32ole.prg

Harbour
contrib\xhb\xhbole.prg
contrib\hbwin\oleauto.prg

... refirió a una fila eliminada o a una fila marcada para eliminar. (0x80040E23): Microsoft Cursor Engine

Stack Calls
===========
Called from: => TOLEAUTO:VALUE( 0 )
Called from: .\source\function\ADOFUNCS.PRG => FWADOFIELDSTRUCT( 2069 )
Called from: .\source\classes\XBROWSE.PRG => TXBROWSE ...

... from c:\bcc7164\include\windows\sdk\windows.h:260:
In file included from c:\bcc7164\include\windows\sdk\ole2.h:39:
c:\bcc7164\include\windows\sdk\oleauto.h:1057:56: warning: redefinition of typedef 'LPTYPELIB' is a C11 feature
[-Wtypedef-redefinition]
typedef /* [unique] */ __RPC_unique_pointer ...

... TMSGITEM
23 TTIMER
24 TDATAROW
25 TDIALOG
26 TPANEL
27 TSCROLLPANEL
28 TSAY
29 TGET
30 GET
31 TCLIPGET
32 TBUTTON
33 TBUTTONBMP
34 WIN_OLEAUTO
35 TOLEAUTO
36 FWMARIACONNECTION
37 TXBROWSE
38 TXBRWCOLUMN
39 TCLIPBOARD
40 FWROWSET
41 FWMARIAROWSET
42 TFIELD
43 TFIELDS
44 TMDICHILD ...

Ok, thanks Antonio.

Fivedit can use the Fivewin standard debugger, selecting the /b option when compiling or simply adding at the beginning of their prg that they want to apply debug the #pragma /b+.

https://i.postimg.cc/MK7BvjL6/Fivedit0101.png

https://i.postimg.cc/cJbgV7vm ...

Perfect, I'll take a look, thanks.

Antonio Linares wrote:FWH has its own debugger, you only have to build using /b, in example:

buildh tutor01 /b

It works with FWH only, because it uses FWH components

FWH has its own debugger, you only have to build using /b, in example:

buildh tutor01 /b

It works with FWH only, because it uses FWH components

Thanks, but I was only interested in FiveTech, to see if it has internal debugging capabilities.

The errors are regarding FIVs, as in fivedit17.fiv. The 'i' looked like an 'l' with the font I have.

Anyway, I think I see what the problem is. FivEdit expects to be in the C:\FivEdit folder. I have it ...

Thanks, Antonio.

Does FiveEdit have Single-stepping capabilities? I tried using it, but it keeps complaining about missing FLVs when it loads, even though all of the bundled FLVs are in the same directory as the FiveEdit executable.

Regards,

Excuse me, what are FLVs?
If you want to learn how to ...

You can use Microsoft vscode + Harbour debugger extension from Antonino Perricone

Thanks, Antonio.

Btw, which is a good GUI debugger for Harbour? The default console debugger is ok but sometimes inconvenient, especially when you have 2 monitors. If you try to move the debugger to the larger non-default monitor, all of the lines get skewed & unreadable.

I'm using a third party ...