FiveTech Software tech support forums

Marc & Karinha
Thanks for your suggestions.

I've used your ideas plus a few of my own to add enhancements to errsysw.prg which I hope will help me catch possible network errors.

Thanks again.

Don

I'm having trouble with a customer application which seems to loose its network connection from time to time.

Does anyone know of a technique that will allow me to test if a workstation is still connected to a LAN?

Don

Trying new ideas to see if I can learn about what's creating my problem. This line would not properly alter oValue from numeric or date formats to string. oValue := tGet():Redefine( , bSetGet := {||mValue } , oQry_Dlg, ,"@S30" , , , , , , ,True, , ,False ) The line seems to execute properl...

I have a GET define so: REDEFINE GET oValue VAR mValue ID 2105 of oQry_Dlg ; on change ( iif(! oSave:lactive, Set_Save() ) ) ; update Whenever the value of mValue becomes numeric the picture of oValue is changed as in the next line. oValue := tGet():Redefine( , bSetGet := {||mValue }, oQry_Dlg, ,&qu...

There are 19 controls on this one dialog.

Hi, Antonio.

FWH Ver 13.03

I found the solution this morning.

These did not work:
valid( !empty(cSS_NUM) )
valid( !empty(oSS_Num:Value()) )

This DID work:
oSS_Num:bvalid := { !empty(oSS_Num:Value()) }

valid ( empty(cSS_Num ) )

valid ( if(empty(cSS_Num ),.F.,.T.) )

Both versions return False regardless of what may be entered by the user.

I did a poor job of describing my problem.

Since upgrading the FWH\Harbour the valid statement always finds cSS_Num empty, regardless of whatever the user may enter.

REDEFINE GET oSS_Num VAR cSS_Num ID 2103 of oFld:aDialogs[GenFldr] ; Picture "@R ###-##-####" ; valid ( !empty(cSS_Num ) ) ; UPDATE Need to be sure that the user can't save a blank value to cSS_Num. This used to work just fine in earlier versions of my system before I upgraded FWH/Harbour....

Brilliant, Antonio, it worked!

I had tried that but with the space btw the '2' and '>.'

Thanks!

I couldn't make it work either, Antonio.

For now I'm just going to be content to wait for the official Harbour version.

Yes, Antonio, I would love to have that feature as soon as it is available.

My goodness, Antonio, I hadn't expected you to go to all that effort. Thank you! If it makes sense to add the ability to direct warnings to a text file to future versions of Harbour, please do. In the meantime I'll find another way of capturing the warnings. Again, thanks for your help. Saludos, Don

Yes, I did. $(HBDIR)bin\harbour $< /n /w2 /o$(CSRCDIR) /i$(FWDIR)include;$(HBDIR)include > Warnings.log The actual warnings scroll to the screen. This is what appears in Warnings.log: Harbour 3.2.0dev (Rev. 18881) Copyright (c) 1999-2013, http://harbour-project.org/ Compiling 'e:\aba\aba_4\Locals.pr...

Is there any way that I can force Harbour to write its warnings to a text file?