Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - jaapmurre

Pages: [1]
1
See, the subject line. There seem to be many differences between Excel and Paramquery, to the extent that work-arounds are not even possible. We need to distinguish between 'empty cell' and 'cell with 0'. It seems that JavaScript falsy values are used instead of Excel interpretations.

2
Bug Report / Bug in Excel-like formulas with IF function and <>
« on: May 26, 2020, 12:04:49 am »
This formula gives error 'Unexpected token >' but should not: =IF(B5<>"",IF(B6<>"",0,1),.5)

But this works: =IF(B5<>"",IF(TRUE,0,1),.5) and produces 0

Perhaps the parser chokes on repeated <>. E.g., this also produces Unexpected token >:

=AND(B5<>"",B6<>"")


3
Just noticed that the same problem occurs with numbers in scientific notation: 1.0973e-37. My guess would be that there is a regex somewhere trying to guess the type and assuming that only, say, digits and dot . can occur in a number and not also - (and +) and e (and E).
.

4
Does anyone know how to remedy this? When I use the export to Excel (in Paramquery Pro 6.0, with the dataExport function and format .xlsx) it works fine except that all negative numbers (floats and integers) turn out as left-aligned and Excel cell format as Text instead of Number. BTW This is also the case with all official Demos (juist change a few numbers to negative and export). Is there an easy fix? Using 'align: right' does not work/help. Thanks! -- Jaap

Pages: [1]