|
| [WD22] Server latency Client server connection |
| Iniciado por guest, 23,mar. 2018 19:31 - 6 respuestas |
| |
| | | |
|
| |
| Publicado el 23,marzo 2018 - 19:31 |
| Good afternoon, I have a project that connects directly to a HFSQL database on our hosted server but all the queries and h functions sometimes go too slow, and we're having some troubles with our software performance, the next message is shown by the ide "The period of latency to reach the server is high. Therefore, all the accesses to the HFSQL servers are slowed down". Any suggestions as to how solve this problem? |
| |
| |
| | | |
|
| | |
| |
| Publicado el 23,marzo 2018 - 22:15 |
Hello Luis,
It looks like a slow internet connection. It says that it can't reach the server fast enough.
We never had this message. Even on a slow connection.
There is a function in windev to test the connection quality.
HConnectionQuality |
| |
| |
| | | |
|
| | |
| |
| Publicado el 23,marzo 2018 - 22:16 |
| Thanks frans! I'll check this out |
| |
| |
| | | |
|
| | |
| |
| Publicado el 23,marzo 2018 - 22:21 |
| Other question Frans, it just threw me a number but I don't know what to compare it to, the help doesn't help. I got 1614187, what does this means? |
| |
| |
| | | |
|
| | |
| |
| Publicado el 24,marzo 2018 - 13:29 |
Hi Luis,
What version is your HFSQL Server and what version is your WINDEV app?
Generally, you must NEVER use (say) a version 21 WINDEV application with a v20 (or 19 etc) HFSQL Server.
The HFSQL server must be GREATER or EQUAL to WINDEV.
I have seen "unknown errors" in the above situation.
Regards
Steven Sitas
www.alpha360.biz |
| |
| |
| | | |
|
| | |
| |
| Publicado el 27,marzo 2018 - 18:04 |
| Hello Steven our HFSQL and Windev are the same version, version 22 |
| |
| |
| | | |
|
| | |
| |
Miembro registrado
28 mensajes |
|
| Publicado el 28,marzo 2018 - 11:40 |
Another 2c worth:
I have found that running a WinDev (thick client) app over anything but a local lan can run into serious performance issues when running large queries and reports. I usually end up using RDP for these users. Alternatively find a way to run the queries on the server (stored procedure or such) and only send the final results for display to the client. |
| |
| |
| | | |
|
| | | | |
| | |
|