Bruce

>I appreciate the quantity and quality of the answers, clearly "Bite the bullet and get on with EDB".

Being a new project should make it bit easier - no data to convert. Is it going to be mainly table or mainly SQL based?

Roy Lambert

Roy,

<< What's a large table? Are we talking 10k rows, 100k, 1m or what? >>

10-100 million rows.

<< The other thing that occurs to me now is what's the c/s performance comparison? I know you don't like speed comparisons but do you have any idea? >>

It depends upon what you're doing.  If you're doing SQL, then you won't notice much difference until the result set comes back across.  In general, EDB is better at handling bi-directional row caching for remote session table/result set cursors, which means that it doesn't have to ask the EDB Server for rows as much as DBISAM does.

Tim Young
Elevate Software
www.elevatesoft.com

Tim


><< What's a large table? Are we talking 10k rows, 100k, 1m or what? >>
>
>10-100 million rows.

I'm now going to go and sulk - my biggest is c30k rows

Roy

Now Roy,

We all know size isn't everything.