What is more interesting, that output to the log file knows about decimal separator and it is a different separator (dot), than that set in the "Company date and numeric format" (comma). for example:


2023-02-27 08:52:04 AD WARNING: DecimalSeparator returns blank, failing over to company decimal separator ,
2023-02-27 08:52:04 AD LineNr 2 tstr=110.25 SubTotal=110.25 VAT=756.36 Total=866.61

Hi

the programmers said that It sounds like a bug and you should report it and create backup so that we can repeat

please detail every step. are you doing any company switching in import routine is also question. Probably not but this seems like it fails to load numeric format from the company it is importing in


please tell me if you report it thanks

Hi. Try to use SetCompany(x, false); where x is the target company number, even if there is only one company on the server, before you call DecimalSepator().

Are you calling it inside ImportSalesInvoicesFromArea or before that qupdating function is called?

It is like this. Just checked again. As you can see ImportSalesInvoicesFromArea() forgets DecimalSeparator.

2023-07-04 17:15:48 AD executing WebStoreTabInvoice CurrentCompany=1 DecimalSeparator=,
2023-07-04 17:15:48 AD ImportSalesInvoicesFromArea DecimalSeparator=

global
updating procedure ImportSalesInvoicesFromArea(...)
begin
Logtext(0,"ImportSalesInvoicesFromArea DecimalSeparator=" & DecimalSeparator);
...
end;

global
procedure WebStoreTabInvoice()
begin
LogText(0,"executing WebStoreTabInvoice CurrentCompany=" & CurrentCompany & " DecimalSeparator=" & DecimalSeparator);
qupdating.ImportSalesInvoicesFromArea(..) //removing qupdating helps to remember DecimalSeparator
queued.StoreResultsEMail(Mailr);
end;

global
procedure WebExtraAPI()
begin

...
oldcomp = CurrentCompany;
//if (newcomp!=oldcomp) then begin <- commenting this out didn't help
if (SetCompany(newcomp,false)) then begin
WebStoreTabInvoice();

end;
end;