Possible Issues and Solutions

 

Since LyciaWeb is a web client, it is dependent on the web browser which is used to run it. Some browsers may have conflicts or contradictions with the workflow of a 4GL program. Mainly this may touch the keys which may correspond to browser hotkeys and some other issues. This appendix lists all the issues found in various web browsers which may affect the execution of 4GL programs. These are genuine browser bugs or features which hinder some 4GL functionality and cannot be fixed by Querix or do not have a workaround. The list is not complete, it is being updated regularly.

 

Issue: the cache cannot be properly moved or cleared.

You may also get this message in Lycia Studio:

 

[3772:0302/120647:ERROR:cache_util_win.cc(20)] Unable to move the cache

[3772:0302/120647:ERROR:cache_util.cc(132)] Unable to move cache folder

[3772:0302/120647:ERROR:cache_creator.cc(125)] Unable to create cache

 

Possible Solution: Clear the cache manually by deleting the content of the folder where the cache data is stored.

 

How to do it:

 

Settings → Advanced settings → Privacy → Clear browsing data → Cached images and files → Clear browsing data

 

 

 

Settings → Options → Advanced → Network → Cached Web Content → Clear now

 

 

 

Opera → Settings → Privacy & security → Clear browsing data → Empty the cache → Clear browsing data

 

 

 

 

Issue: If you use Google Chrome and have ESET NOD32 AntivirusTM installed on the same machine, the speed of the browser itself and thus of the 4GL applications running in it will be considerably slower. The browser ping may be up to 500ms.

 

Possible Solution: disable HTTP checking.

 

How to do it: double-click on ESET and then press F5 key and after that all what was written Advanced setup... -> Antivirus and antispyware -> Web access protection -> HTTP, HTTPS and uncheck "Enable HTTP checking".

 

 

Issue: Web browsers are not influenced by the system locale settings. So even if you have the Format of dates and numeric values set in your system the application run in Web client will not have access to these settings.

 

Possible Solution: set the browser locate.

 

How to do it: to set the values you need either to specify the correct environment variables in the inet.env file, or set the browser locate directly in the web browser settings.