Bruno,

<< So DBISAM is faster than ElevateDB ...  >>

In your one query, yes.  It really depends upon what you're doing with each
product.  DBISAM is simpler than ElevateDB, so ElevateDB has to do quite a
bit more work than DBISAM (per-column collations, proper RI and constraint
management, SQL triggers).  Also, there is the dual-mandate of native Win32
and .NET managed code with ElevateDB, so we cannot use pointers in
ElevateDB, whereas DBISAM is nothing but pointers.  That causes some call
overhead that contributes to lesser performance *in some cases*.

<< What is the interest of moving ElevateDB if not faster ? >>

You'll have to compare more than one query to determine that.  ElevateDB's
feature set is much, much larger than DBISAM's.

--
Tim Young
Elevate Software
www.elevatesoft.com

OK,

Thanks for all this answer.

I will migrate my applications to ElevateDB and see what it gives

Have a Good day

LOL.

You'll never convince me of that one either.  In modern RDBMS systems Null
<> Empty String and is SQL standard as far back as ANSI SQL 92.  Regardless
of DBISAM's support of it, I still would have a hard time with at least this
one.

Lance


"Roy Lambert" <roy.lambert@skynet.co.uk> wrote in message
news:94A4AF39-FCAF-45C5-94AA-7F0460C16664@news.elevatesoft.com...
> Lance
>
>
>>SQL compliancy,
>
> All I have to do is persuade him that NULL can = emptystring and I'll be
> happy <vbg>
>
> Roy Lambert

Lance


Really? Why?

Roy Lambert