FiveTech Software tech support forums

Isn't it easier for you to post the faulty SOURCE or send the FiveTech team for analysis?

Oun stops the program line by line to find where it hangs.

Regards, saludos.

Antonino, You are right. My mistake was based on the faulty mod_harbour modpro results: https://www.modharbour.org/modharbour_samples/modpro/modpro.prg Curiously enough, that code fails as I said when running it from modpro. I wonder ...

... all claims to be professionals. Might I suggest we remove ( once again ) posts that attack other programmers personally or claim their work is faulty. I believe Antonio had to address the same type of behavior previously with Silvio regarding others who have created programs he claimed were ...

... is an Intel one. Also, in my opinion it´s not a good image when the user downloads a demo and he can´t run it. In most cases he would discard such faulty software, and thus loosing customers. In fact, modern antivirus tend to mark such software as potential damage and they block it. It´s quite ...

... and how with 2012 it works even w/out doing this check. I can, however, understand how some code will eventually fail if it is different or "faulty" from the beginning. I can perfectly understand how this is not xbrowse's fault. I apologize. Having said that, I think the action taken ...

Günther,

I agreed with your idea that the oGet not had to be created always

but really, had no time to do deeper in your code, and mine was faulty, so yes, I agree that we are closer now

My tests are ok, please try yours and lets see if this is already solved, thanks

... problems with (try to remember): WITH OBJECT obj SomeArr[:Someproperty] ==> SomeArr[Obj:SomeProperty] END 4) Xharbour has no problems with (faulty) expressions as : obrw:bPastEof() oDlg:end It can be very dificult to find such error , see http://forums.fivetechsupport.com/viewtopic.php?f=3&t=24820#p134633 ...

... If we need syntax compatibility with xharbour, we need to include xhb.ch in the program file and link it with xhb.lib. The logic I posted above is faulty. Here is the corrected one #include "Fivewin.ch"#ifndef __XHARBOUR__#include "xhb.ch"#endiffunction main()  ...

... 1 ]:lBtnTransparent := .T....  This error triggers if nMarqueStyle := MARQSTYLE_HIGHLROWRC and oCol:lBtnTransparent := .T. BUG? or my faulty declarations :lol: Any workaround? Regards, Frances

... in DICOM, and we can ensure that is correct with the PadR function. But if the length is not 8 our code setting up the DICOM VR is presumably faulty. Should we rather return an error somehow to the requesting code? And if we are going to check for errors do we check the string for only containing ...

You may have a faulty network card.

EMG

Believe me: a faulty network card can cause unexpected results.

EMG

I never noticed that behavior. I think it could be something wrong in the network (a faulty network card?).

EMG

Carlos, Uwe

Both solutions works fine.
... sorry I completely forgot I was using a MDI Window, my mistake.
.. I guess I'll have to rest some days, I have some faulty IRQ's


Thanks a lot

From Chile
Adolfo

Dutch,

The error message that you posted suggests that one of the Workshop DLL's might be faulty or corrupted somehow. If you can identify that DLL (I couldn't quite read its name on your error message) then maybe you can replace it.

- Roger