Error 9015

[Randal]

All,

I'm getting an "Unrecoverable error 9015" "Symbol item expected from hb_vmDo()" . No error log is generated. The error occurs when trying to call r&r report writer although no error log is generated and I don't know exactly where the error occurs.

Using xHarbour Nov 2015 Build 119 and FWH 13.02. Is this verison of xharbour compatible with this verison of FWH?

In the past I've had to link send32.lib and mem32.lib and chkstk.prg. Are these files still required or do I need updated FWH libs/files to work with this verison of FWH?

Any way to track down where this error is coming from?

Thanks,
Randal

[Antonio Linares]

Randal,

I suggest you to use Harbour. It seems to me as a corruption issue.

That xHarbour version is two years older than FWH 13.02

Yes, those libs are still needed.

How are you calling r&r ? Could you post an example to test here ?

[Randal]

Antonio:

Thank you for your quick reply.

Randal,

<<I suggest you to use Harbour. It seems to me as a corruption issue.>>

I would like to consider migrating to Harbour however, this will take some time and I need to fix this error now if possible.

<<That xHarbour version is two years older than FWH 13.02>>

I think you mean the other way around, i.e. the FWH version is 2 years older than the xHb version. Would upgrading FWH solve this issue? Is it possible the newer xHb libs are not compatible with the the older FWH libs I'm using?

<<How are you calling r&r ? Could you post an example to test here ?

>>

Just using Winexec. This has worked for years. I have one customer that has several users connecting via RDP. It's only these users that have a problem, i.e I am unable to recreate the problem here.
From any of the local computers it works fine. I did recently upgrade this customer to xHb Nov 2015 so I don't know if that has anything to do with it.

I don't know exactly where in the print process it crashes as no log file is created. Is there anyway to trap this error?

Thanks,
Randal

[Antonio Linares]

Randal,

If you don't call WinExec() then there is no error ?

[Randal]

Antonio:

It's hard to say. I cannot recreate the error at my end and no error log is generated. I guess I'll sprinkle the code with some msginfo calls and see if I can pinpoint the offending code.

Thanks again,
Randal

Randal,

If you don't call WinExec() then there is no error ?