... Can be used to compare strings as well as any valtype. Syntax-1: FW_StrICmp( uVar1, uVar2, [lExact] ) --> -2/-1/0/+1/+2 lExact defaults to SET EXACT setting. uVar1 and uVar2 can be of any data types. In case both are strings, "case insensitive" comparision is made. In other cases, ...
... así como cualquier tipo de dato. Sintaxis - 1: FW_StrICmp( uVar1, uVar2, [lExact] ) --> -2/-1/0/+1/+2 lExact por defecto el valor de SET EXACT. uVar1 y uVar2 pueden ser de cualquier tipo de datos. En caso de que ambos sean cadenas, se realiza una comparación "insensible a mayúsculas ...
... Can be used to compare strings as well as any valtype. Syntax-1: FW_StrICmp( uVar1, uVar2, [lExact] ) --> -2/-1/0/+1/+2 lExact defaults to SET EXACT setting. uVar1 and uVar2 can be of any data types. In case both are strings, "case insensitive" comparision is made. In other cases, ...
When you set filter with oDbf:SetFilter( cFilter, aParams ) The method applier the aParams to cFilter and prepares the filter string to set the filter. You can check the exact filter string with ? oDbf:DBFILTER() and see if this is what you expected.
... for our documentation, and yet I find that my clients rarely, if ever, read the manual, even when a press of the F1 key will make it open to the exact page needed. They have lots of excuses, but that never includes a comment that says the information presented wasn't helpful. It's always they ...
... In my main application, I include errsysw.prg and it works perfectly when an error occurs. I have a subset of my program, using many of the exact same files from the same source directory. When an error occurs, instead of errsysw showing a popup screen with the error and all the data, the ...
... does not work well because it is based on the fivewin Tcontrol class so that the drag of the objects (dots) are not where they should be and makes exact movement difficult, this happens if you want to draw an invoice with precise lines and boxes as I wrote above there must be a parent class such ...
it seems to be working now!! we already tried both examples that Mr Rao posted previously and now they are returning the exact same result! Tomorrow morning we'll try it in our application, and hopefully it's going to be ok. Thank so much!! You said that the main problem is related ...
... )USE CUSTOMER EXCLUSIVEFW_CdxCreate()CLOSE CUSTOMER In your filter expression, references to the fields should match the exact expression used in the indexes. For example, Because we created index on UPPER(CITY), SET FILTER TO UPPER(CITY) = "A" // optimizedSET ...
... when I return, its ready. This is too bad. It can not be like this. Size of 300,000 records is nothing. We can not comment unless we get into the exact code. Do you have too many deleted records? In that case the performance can be very sluggish. Try packing the DBF and then run. Indeed, I had ...
... when I return, its ready. This is too bad. It can not be like this. Size of 300,000 records is nothing. We can not comment unless we get into the exact code. Do you have too many deleted records? In that case the performance can be very sluggish. Try packing the DBF and then run.
... wrong results! (different in tprinter and fwpdf) An other interesting effect is the print from transparent PNGs: In tPrinter gives in the preview exact transparent pictures but in the real print the transparence is lost. Printing the PDF-file from fwpdf is correct and transparent!