FiveTech Software tech support forums

nDataLines is used by xbrowse only while creating the browse for the first time for calculating the row height. After creation of the browse. i.e., during runtime, it is never used and changing the values does not do anything. During runtime, you can change the data ...

nDataLines is used by xbrowse only while creating the browse for the first time for calculating the row height. After creation of the browse. i.e., during runtime, it is never used and changing the values does not do anything.
During runtime, you can change the data oBrw:nRowHeight.

You create a RC file using a visual RC designer and then use it from your FWH app

You can use the one provided in Visual Studio Community, ResEdit, PellesC, etc there are many availables

You visually "draw" your screens instead of calculating coors by try and error...

... importance. From these considerations we can enunciate the following definition: The cyclometric distance between two numbers is obtained by calculating the arithmetic difference (major minus minor); if the result exceeds "the limit" 45, the latter is subtracted from the fixed 90. ...

... for the cyclometric sum it is always necessary to subtract 90 if the sum exceeds 90 The cyclometric distance between two numbers is obtained by calculating the arithmetic difference (major minus minor); if the result exceeds "the limit" 45, the latter is subtracted from the 90 set. ...

Xbrowse needs correct tuning to work the best. Correct use of : set filter to, set relation to, Ordscope's .... Correct setup of indexes... Calculating fields slows down Colors are only repainted in the screen that you see, so that should not matter to much. I also have speed issues a moments, ...

Silvio: I think that in the first case you are calculating "days" ie From 2021-06-19 to 2021-06-20 are two days but if you count "nights" it shoud be one night. My five cents. Regars here is a chalet and the owner sale umbrellas ...

Silvio:

I think that in the first case you are calculating "days" ie

From 2021-06-19 to 2021-06-20 are two days but
if you count "nights" it shoud be one night.

My five cents.

Regars

... RoundBox(), and Ellipse() is to enable specifying the text to be printed inside the box. The text can be multi-line and multi-fonts. This avoids calculating the precise position and using Say() to print the text at the correct position. Example Code:    oPrn:RoundBox( 1.0, 1.0, ...

... _Isearch( oLname1, cLname1, oCid1, cCid1, oSceis1, cSceis1, oLbx, oDbf ) Also, are you passing both the field object and the data, then calculating the data also? If so, why? And why do you put the number "1" at the end of every fieldname? James

... solutions. for me only in this way the user could customize each price because doing as I was advised some time ago by the experts you risk not calculating the right rate well

What happens if you change the function to: Function GetDayofPeriod(dDateFrom,dDateTo,aListini)     Local n //reset days For n=1 to len(aListini)  aListIni[n][5]:=0 nextFor n=1 to len(aListini)    IF d >= aListini[n][1] .and. d <= aListi...

Perhaps the error not is there ... This morning I saw the dateTo is wrong on a my function to update the dates after a modify I have these lines local dStart:= uCharToVal(dDataIniziale, "D" ) local dEnd:= uCharToVal(dDataFinale, "D" ) If I select the from 10 July to 14 July and t...

What happens if you change the function to: Function GetDayofPeriod(dDateFrom,dDateTo,aListini)     Local n //reset days For n=1 to len(aListini)  aListIni[n][5]:=0 nextFor n=1 to len(aListini)    IF d >= aListin...

I have 4 date ranges (periods) I have two dates and I want to calculate the number of days for each period. local dcheck_in: = ctod ("17/05/2020") local dCheck_out: = ctod ("17/06/2020") if I do the operation dCheck_out-dcheck_in i get 31 days in the calculation function for the ...