Hi

i'm using EDB 2.02 Build 10 + Delphi 2009

Any clients have call me for "slow problem" when open any procedure of my
application.


i have add a log in the open procedure ( time : BeforeOpen - AfterOpen ) of
my application

( all TEDBTABLE , network enviroment , NO C/S )


in my log anytime ( 1 / 10 ) there a table ( Table with 2 only fields ,
too )

take 0.50  - 0.90 seconds for open.
all other table take 0.02 - 0.10 for open.

No calc fields
No fields lockup / calc..
Notting...

This time are take with a clear network ( Fast , new pc , no AV )

with notthing of heavy on the network.

only 2 pc :
pc 1 - open all my function for open table ( windows disabled
optimistic-cache... )
pc 2 : open my function for get Time.


NOTE
The problem of slow appear when the table is not open , before.
Only the first time of the table is opened, there is slow problem.

if the table was already open ( in other form ) , open Table required always
Zero Time 0.00

with DBISAM is was always fast, no problem.


sorry for my bad English

Mauro


Is this behaviour replicable with a new project with just this table and no visual controls?

Roy Lambert [Team Elevate]

> Is this behaviour replicable with a new project with just this table and
> no visual controls?

There tables don't have datasource , No visual control.

Mauro


OK but it would still be good to know if the behaviour is the same when nothing else is involved.

The second thing to try is to turn off all av on all PCs involved and see what happens.

Roy Lambert [Team Elevate]

> The second thing to try is to turn off all av on all PCs involved and see
> what happens.

Hi Roy  

DbIsam was most fasted  of EDB 2 in Open Table

i and all my clients ( 400 ) know it.



In the Query - Filter .... EDB is GREAT !! , always better of dbIsam
but in open table is not much optimized.



It is not a particolar situation of my PC      ( A.V. ...... )

Much forms of my program open with TDbgrid in full screen

with DbIsam the form-show is VERY ULTRA FAST     

with EDB .... medium........

Mauro


I understand what you're saying but you're giving nothing to help to try and solve the problem. If one table is opening slower than others there has to be a reason. To find that reason will take a bit of research which, since its your app and your data is going to have to be carried out by yourself. I'm prepared to have a look but to do so I'd need the app and data.

Whilst I was using DBISAM I found the single most influential thing in terms of opening tables was the visual controls they were connected to, the second the relationships to other tables - ie wether they were doing or were used in lookups.

The only way to determine if its something about the table itself is to try opening it in isolation in a project containing nothing else.

If that's as fast as other tables then it has to be the structure of your app or the environment. You are dismissing both of these without carrying out (or at least reporting on the newsgroups) any diagnostics to prove the issue.

Things may have been faster under DBISAM but its possible that in the conversion you've done something which has had an impact, or not done something which would have had an impact. I certainly know from my own conversion that things are different.

If opening the table in a new project in isolation is also slow then you need to ship the catalog and the problem table to Tim to have a look at.

Roy Lambert [Team Elevate]