FiveTech Software tech support forums

James,

yes, you're right, that's what 'solved' the problem. Tests with about 200,000 records and olb:refresh took up to 3 seconds per dbseek, whereas olb:select(0) and select(1) only take up to 0.2 seconds at most.

But indeed, we are already considering, if it's useful to wait about half a second, if there follows another keystroke, and if not, then do the dbseek.

Gilbert,
as far as I understood not xBrowse was the problem.
Would you be so kind to change the topic.
Your topic is like a statement and someone not reading the whole thread could get the impression that xBrowse is slow.
But my tests do not confirm this statement. xBrowse is indeed a fast browser.
Regards,
Otto

Otto,

as far as I understand, oBrw:Refresh() is a xBrowse-Method (when oBrw is a xBrowse-object). So the performance problem is directly linked with xBrowse. But we found a solution to improve performance a lot. So I think, the topic still is ok.
But I want to share a better solution than I posted before. Instead of

Code: Select all  Expand view

oBrw:Select(0)
oBrw:Select(1)

we now use

Code: Select all  Expand view

oBrw:GetDC()
oBrw:Paint()
oBrw:ReleaseDC()

Gilbert,

Why don't you just use oBrw:Refresh() ?

Antonio,

because oBrw:Refresh() made our search very slow (in network with a big database, when the database is in use at more than one computer simultaneously)
That was the outcome of our search, why xBrowse was slow.

On our testing system, oBrw:Refresh() still takes up to 3 seconds, while oBrw:Paint() takes about 0.1s