FiveTech Software tech support forums

I keep having display problems, there are about 6500 records in the archive and each record has 57 fields.
the size of the dbf archive is about 757 bytes
If I open the dbf with EmagDbu or with fwdbu I have no problems
I am using Tdatabase and scrolling is very slow
how can i improve the visualization?

Silvio, you should include in your software the
Benford's Law and Euler's number into your software for prediction.

Also the integration of AI would be interesting. Yes, even very interesting.

viewtopic.php?f=3&t=41605

Best regards,
Otto

Otto wrote:Silvio, you should include in your software the
Benford's Law and Euler's number into your software for prediction.

Also the integration of AI would be interesting. Yes, even very interesting.

viewtopic.php?f=3&t=41605

Best regards,
Otto

I not know it

Silvio, you made a beautiful design.
This looks superb.
Best regards,
Otto

Hi Silvio,
Try to remove all the frills colors, filters or view the records in a simple way,
maybe even just one city at a time, then enter one thing at a time hoping to
understand who slows down the display.
it is a way of proceeding not as a computer scientist but as a policeman but
the point is to solve the problem, we are not Nages.

TIA

mauri.menabue wrote:Hi Silvio,
Try to remove all the frills colors, filters or view the records in a simple way,
maybe even just one city at a time, then enter one thing at a time hoping to
understand who slows down the display.
it is a way of proceeding not as a computer scientist but as a policeman but
the point is to solve the problem, we are not Nages.

TIA

this morning I realized that maybe xbrowse doesn't work well, that is I took an example of Nages and I put a dbf with 106353 records in it
the search is very very very very very slow, too slow
so xbrowse works for small archives even if I have 9000 records in another program and it runs fine

Xbrowse needs correct tuning to work the best.

Correct use of : set filter to, set relation to, Ordscope's ....
Correct setup of indexes...
Calculating fields slows down
Colors are only repainted in the screen that you see, so that should not matter to much.

I also have speed issues a moments, but more in case of networking. (Can be related to network setup)

I think if mr. Rao would be so kind of making a Sticky-Topic : Xbrowse Best speed performance
many users of the forum could benifid from it.

There have been many postings on speed issues, but Mr. Rao is the right person to setup this post.

Marc,
>Can be related to network setup

Have you tried RemoteDesktop?
If not, you should.
It is also a good preparation for web programming as you change your way of thinking about data access.

Best regards,
Otto

Hola,

Nuestros browses van a ser lentos siempre que se muestren pocos entre muchos registros.
Por desgracia no uso xBrowse (llegó cuando ya tenia todo montado) y si utilizo SBrowse.

Utilizo busquedas con wildcards OrdSeekWild() que precisamente presentan el escenario antes descrito: En grandes .dbf muestran pocos registros, con lo cual un set filter ahi puede ser mortal.

¿ Como lo solucione ?

1º Presento el sbrowse en dbf
2º El usuario realiza la busqueda
3º Relleno un array con los recnos encontrados en la anterior busqueda
4º Le doy la vuelta al sbrowse que pasa a ser un sbrowse de array (el de los resultados)

Va como un avion y el usuario no percibe absolutamente nada. Cuando el usuario borra el texto en el get de busqueda entonces el sbrowse vuelve a ser sobre una .dbf

Salu2

I am using Tdatabase and scrolling is very slow

Always working directly with DBF is faster than working through TDataBase.
Still it will not be VERY SLOW. Only a little slower.
To reduce the speed differences, you may use

Code: Select all  Expand view

oDbf:lBuffer := .f.
 

Normal speeds of scrolling DBF data with 100,000 records with XBrowse:
Single line scrolling, Page scrolling and Scrollbar scrolling:



This speed is definitely not slow.
Even using TDatabase, you should not notice much difference.
If it is conspicuously slow, then examine:
1. Data access speeds (nothing to do with xbrowse)
2. Complex filters.
3. Most likely, your own program.

Zoom/Unzoom speeds of 100,000 records DBF.

Nages,
If we try with xbrowser oDbf it is fast no problem
If we insert a xbrowse into a dialog as the test sample I sent you it is too slow