The following is what we've got coming for ElevateDB in the next two months.
The order in which the items appears is also the order in which they are
planned to be done:

- 1.07 release, including the .NET 2.0 Data Provider with complete Visual
Studio 2005 integration and VCL.NET support for RAD Studio 2007

- Unicode releases for C++Builder personalities of RAD Studio and Borland
Developer Studio

- Searchable manuals on the web site, and HTML Help for all utilities and
product manuals that are now included in WinHelp format

- Replication and cached updates

After the replication is completed, I will be starting development work on
the enterprise server for EDB.

As always, the above is subject to change, if the need arises due to
priority shifts.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,
great news!
I just need to write an .net application that must share data with other
Delphi Applications.....
One question: I need to modify an application developed in Windev/Webdev,
and I can talk with EDB or DBisam only via Oledb; What I need for this? Your
data provider is even an Oledb provider?
Thanks in advance!

Stefano Monterisi

>
> - Replication and cached updates
>
Replication sounds good!

Can you give any details on this yet?

Will I be able to setup a 'Master' server and link this to multiple 'Slave' servers.

Kind regards, Stuart
Mode Retail Ltd

I see no mention of the return of the beloved IF EXISTS........

Roy Lambert

Stefano,

<< One question: I need to modify an application developed in Windev/Webdev,
and I can talk with EDB or DBisam only via Oledb; What I need for this? Your
data provider is even an Oledb provider? >>

What do you mean by "Windev/Webdev" ?  The ElevateDB .NET data provider is
an ADO.NET 2.0 compliant data provider, which means that it can be used with
the object factories in ADO.NET 2.0 and higher as a generic data provider.

--
Tim Young
Elevate Software
www.elevatesoft.com

Stuart,

<< Can you give any details on this yet? >>

Not entirely, no.

<< Will I be able to setup a 'Master' server and link this to multiple
'Slave' servers. >>

That's one of the target features, yes.  Basically it will work on a
publish/subscribe basis.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,
I explain:
"> What do you mean by "Windev/Webdev" ?  The ElevateDB .NET data provider
is
> an ADO.NET 2.0 compliant data provider, which means that it can be used
> with the object factories in ADO.NET 2.0 and higher as a generic data
> provider.

OK. This, for my VS project is a great new.

Windev is a french development tool that can connect some database natively
and all other databases via Oledb.
I need (for another project) to connect Windev with EDB(or latest Dbisam
release) via Oledb.
I can?
There is an Oledb provider?
Thanks
Stefano Monterisi




>
> --
> Tim Young
> Elevate Software
> www.elevatesoft.com
>
>

Stefano,

<< Windev is a french development tool that can connect some database
natively and all other databases via Oledb. >>

Duh, I actually knew that.  I remember WinDev from way back.

<< I need (for another project) to connect Windev with EDB(or latest Dbisam
release) via Oledb. >>

There isn't an OLEDb provider, but you can use the OLEDB->ODBC bridge with
our EDB and DBISAM ODBC drivers to access EDB or DBISAM databases.   It's
not the best connectivity option, but it works okay as long as you stick
with client-side cursors (disconnected model) and don't try to use
server-side cursors.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim,

> There isn't an OLEDb provider, but you can use the OLEDB->ODBC bridge with
> our EDB and DBISAM ODBC drivers to access EDB or DBISAM databases.   It's
> not the best connectivity option, but it works okay as long as you stick
> with client-side cursors (disconnected model) and don't try to use
> server-side cursors.
Ouch!! I already known Oledb-odbc bridge............
Ok.
Good job

PS.: How about performance with new ado.net provider?

Stefano Monterisi

Stefano,

<< PS.: How about performance with new ado.net provider? >>

I haven't done a whole lot of testing, but my informal tests show that after
application loading time, the actual query execution, etc. is about the
same, maybe slightly slower.

I'll be doing more exacting comparisons as we move along with the .NET
development.

--
Tim Young
Elevate Software
www.elevatesoft.com