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
Search found 63 matches
- Tue Jun 23, 2015 12:30 pm
- Forum: FiveWin for Harbour/xHarbour
- Topic: Test network connection?
- Replies: 4
- Views: 1069
- Mon Jun 22, 2015 5:39 pm
- Forum: FiveWin for Harbour/xHarbour
- Topic: Test network connection?
- Replies: 4
- Views: 1069
Test network connection?
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
Does anyone know of a technique that will allow me to test if a workstation is still connected to a LAN?
Don
- Sat Jun 29, 2013 12:54 am
- Forum: FiveWin for Harbour/xHarbour
- Topic: Changing data type and picture in GET
- Replies: 1
- Views: 822
Re: Changing data type and picture in GET
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...
- Fri Jun 28, 2013 12:34 am
- Forum: FiveWin for Harbour/xHarbour
- Topic: Changing data type and picture in GET
- Replies: 1
- Views: 822
Changing data type and picture in GET
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...
- Fri May 17, 2013 10:08 am
- Forum: FiveWin for Harbour/xHarbour
- Topic: Validate get
- Replies: 10
- Views: 1356
Re: Validate get
There are 19 controls on this one dialog.
- Fri May 17, 2013 9:05 am
- Forum: FiveWin for Harbour/xHarbour
- Topic: Validate get
- Replies: 10
- Views: 1356
Re: Validate get
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()) }
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()) }
- Fri May 17, 2013 1:03 am
- Forum: FiveWin for Harbour/xHarbour
- Topic: Validate get
- Replies: 10
- Views: 1356
Re: Validate get
valid ( empty(cSS_Num ) )
valid ( if(empty(cSS_Num ),.F.,.T.) )
Both versions return False regardless of what may be entered by the user.
valid ( if(empty(cSS_Num ),.F.,.T.) )
Both versions return False regardless of what may be entered by the user.
- Thu May 16, 2013 10:27 pm
- Forum: FiveWin for Harbour/xHarbour
- Topic: Validate get
- Replies: 10
- Views: 1356
Re: Validate get
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.
Since upgrading the FWH\Harbour the valid statement always finds cSS_Num empty, regardless of whatever the user may enter.
- Thu May 16, 2013 8:13 pm
- Forum: FiveWin for Harbour/xHarbour
- Topic: Validate get
- Replies: 10
- Views: 1356
Validate get
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....
- Mon Apr 29, 2013 11:34 am
- Forum: FiveWin for Harbour/xHarbour
- Topic: Upgrading FWH/xHarbour & VS 2010
- Replies: 44
- Views: 9671
Re: Upgrading FWH/xHarbour & VS 2010
Brilliant, Antonio, it worked!
I had tried that but with the space btw the '2' and '>.'
Thanks!
I had tried that but with the space btw the '2' and '>.'
Thanks!
- Thu Apr 25, 2013 3:59 pm
- Forum: FiveWin for Harbour/xHarbour
- Topic: Upgrading FWH/xHarbour & VS 2010
- Replies: 44
- Views: 9671
Re: Upgrading FWH/xHarbour & VS 2010
I couldn't make it work either, Antonio.
For now I'm just going to be content to wait for the official Harbour version.
For now I'm just going to be content to wait for the official Harbour version.
- Thu Apr 25, 2013 1:24 pm
- Forum: FiveWin for Harbour/xHarbour
- Topic: Upgrading FWH/xHarbour & VS 2010
- Replies: 44
- Views: 9671
Re: Upgrading FWH/xHarbour & VS 2010
Yes, Antonio, I would love to have that feature as soon as it is available.
- Wed Apr 24, 2013 3:27 pm
- Forum: FiveWin for Harbour/xHarbour
- Topic: Upgrading FWH/xHarbour & VS 2010
- Replies: 44
- Views: 9671
Re: Upgrading FWH/xHarbour & VS 2010
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
- Wed Apr 24, 2013 12:25 pm
- Forum: FiveWin for Harbour/xHarbour
- Topic: Upgrading FWH/xHarbour & VS 2010
- Replies: 44
- Views: 9671
Re: Upgrading FWH/xHarbour & VS 2010
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...
- Wed Apr 24, 2013 10:31 am
- Forum: FiveWin for Harbour/xHarbour
- Topic: Upgrading FWH/xHarbour & VS 2010
- Replies: 44
- Views: 9671
Re: Upgrading FWH/xHarbour & VS 2010
Is there any way that I can force Harbour to write its warnings to a text file?