Hello Ray,

A little more technical details can help the OO Base team more
efficiently diagnose the problems.

Search times are terrible ( search using the GUI tools )
Copy / Paste as a means to transfer data into Base is horrendous

Your data search through the OO Base GUI is fundamentally a SQL query
statement.
Well, no. I am talking about using the search function. That is not SQL based, instead it iterates over the result set looking for the first match, and it is all on the client side.

Here is a specific example. I have a table that consists of 21 fields, all of type integer or double. The table has 10,000 records. This is a HSQL embedded database, it is running under XP on an AMD 3300+ processor and 640Meg Ram. The table has a primary key field of type integer, and is fully packed ( meaning there are keys from 1 - 19,999 ).

I open that table in a data view and place my cursor in the PK field. I then open the search box ( click on the binoculars ) and enter a search criteria of 2000. Now what would be an acceptable time for that search to find a match - I'm not sure, but I am relatively sure that what I get is not an acceptable time - on average 74 Seconds.

If I use the standard filter this time drops to under 2 seconds. That is most assuredly acceptable, and yes that was done with SQL commands. The problem is, this is a desktop database and many of the users want the ability to browse the adjacent records after the search. In other words they did not want to filter the result set at all, they wanted a search function on the current result set. To add to the problem is the behavior of removing the filter - the result set is reloaded and the record pointer placed back to the first record.

Now that was with a data view - let's look at what happens with a form. If I create a form based on the same table and that form consists of a table grid the same search will run in a just slightly longer time - 76 seconds - But, and here is the real killer. If I create a from that uses individual controls for the field things get much worse.

When the search is performed every control is updated as the bound result set is iterated. EVERY control! The same search now takes 148 seconds to complete.

hmmm - we have a rather nasty thunderstorm roiling overhead so I think I will send this email now, before I get an electrical supply surprise..

I'll follow up a little later.


Sincerely,

Drew

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to