Dear Friends,

New version of the DBISAM ADO.Net Data Provider (ver. 2.0.0) has
been released and is immediately available for download at:
http://www.contextsoft.com/products/dbisamnet/downloads.jsp.

DBISAM ADO.Net Provider v.2 is a separate product, designed
with and for Microsoft .Net Framework 2.0 and ADO.Net 2.0.
This product WILL NOT work under .Net 1.1 and require Visual
Studio 2005 (full or express edition). The previous version
(1.6.0) will still be available for download by the owners of
DBISAM ADO.Net Provider v.2 for use with Microsoft .Net
Framework 1.1, Borland's IDEs and Compact Framework.

The following new features has been added to DBISAM ADO.Net
Provider 2.0.
  - Support for MS.NET Framework 2.0 & ADO.Net 2.0
  - Support for MS VS.Net 2005 (design-time features)
  - Support for .NET Data Provider Enumeration. Please refer
    to this Microsoft documentation for more information on
    this feature of ADO.Net 2.0 framework:
    http://msdn2.microsoft.com/en-us/library/12kxkt25.aspx
    (see installation instruction below on how to configure this feature)
  - Support for ConnectionStringBuilder interface.
    DbisamConnectionStringBuilder let developers programmatically
    create syntactically correct connection strings, parse and
    rebuild existing connection strings. Please refer to this
    Microsoft documentation for more information on this feature
    of ADO.Net 2.0 framework:

http://msdn2.microsoft.com/en-us/library/system.data.common.dbconnectionstringbuilder.aspx

Please, also read more about "What's New in ADO.NET 2.0" here:
http://msdn2.microsoft.com/library/ex6y04yf(en-us,vs.80).aspx

This upgarde is not free. Discounted upgrade price is
available for all existing owners of the previous version of
DBISAM ADO.Net Data Provider (ver. 1.6.0). Customers, who
has purchased DBISAM ADO.Net Data Provider v.1 within 90 days
will receive FREE apgrade as per our 90 days upgrade policy.

For more information, please visit our web site and login
into your account at:

  http://www.contextsoft.com/myaccount

For the history of incidents addressed in each release, please
refer to:
http://www.contextsoft.com/products/dbisamnet/history.jsp

DBISAM ADO.Net Provider is a .Net assembly, implementing
classes and components, required by ADO.Net architecture to
access DBISAM Database Server. It communicates with DBISAM
Database Server using TCP/IP protocol. It is completely
programmed in C# language, which makes it fully managed.

DBISAM ADO.Net Provider does not require any unmanaged dlls,
ODBC drivers or COM components! It is extremely small (only
100Kb!), easy to distribute and requires no configuration!
It can even be built directly into your application!

As an example, of how simple it is to access DBISAM Database
Server from .Net, see SQL Console utility available for free
download at our web site:

  http://www.contextsoft.com/products/dbisamnet/downloads.jsp

These are the main features of DBISAM ADO.Net Provider:
  1. Completely written in C# and is 100% managed code.
  2. DOES NOT require any unmanaged libraries, dlls or other 3rd party client
libraries!
  3. Uses native DBISAM protocol to access DBISAM Server via TCP/IP.
  4. Supports both versions of DBISAM: v3 and v4.
  5. Provides highest performance.
  6. Extremily small footprint (only about 90 KB!).
  7. Easy to deploy (no dlls necessary!).
  8. Supports all DBISAM data types, including BLOBs.
  9. Provides connection pooling (for ASP.Net).
 10. Full C# source code is available.
 11. Includes convinient design-time tools, accessible from VS.Net 2005 IDE

The package also includes demo applications (written in C#
and Delphi and compatible with  Microsoft Visual Studio.Net)
and ASP.Net web pages demonstrating the usage of DBISAM
ADO.Net Provider.

For more information, please refer to our web site at:
http://www.contextsoft.com/products/dbisamnet/package.jsp

Fully functional evaluation version is available at:
http://www.contextsoft.com/products/dbisamnet/downloads.jsp

You can order a registered copy of DBISAM ADO.Net Provider
Suite for only $99.00 at:
http://www.contextsoft.com/products/dbisamext/ordering.jsp

Source code and Compact Framework package are sold separately.
For more information, please go to:
http://www.contextsoft.com/products/dbisamnet

Sincerely,
Michael Baytalsky
e-mail: mike@contextsoft.com
http://www.contextsoft.com

Michael,

>   4. Supports both versions of DBISAM: v3 and v4.

Will V5 be supported when it's out ?

Ole Willy Tuv

>>  4. Supports both versions of DBISAM: v3 and v4.
> Will V5 be supported when it's out ?
That's the plan. Also, I hope we will be able to
support all three versions with same small dll (currently
we support 3 & 4).

Sincerely,
Michael

Michael,

> currently we support 3 & 4.
How did you implement this feature?
I mean how you can open the table from v3 with engine v4 (without table
upgrade from v3 to 4)?

--
With best regards, Mike Shkolnik
EMail: mshkolnik@scalabium.com
http://www.scalabium.com

Hi Mike,

What he means is that the ADO provider can connect to either a version 3
or a Version 4 DBISAM server.

You have to specify which when you setup the connection string.

Chris Holland


Mike Shkolnik wrote:
> Michael,
>
>> currently we support 3 & 4.
> How did you implement this feature?
> I mean how you can open the table from v3 with engine v4 (without table
> upgrade from v3 to 4)?
>
> --
> With best regards, Mike Shkolnik
> EMail: mshkolnik@scalabium.com
> http://www.scalabium.com
>
>

Chris,

I understood. But how Michael implemented this feature?

As I see, he used the DBISAM engine (v4 as I see because he can open the
tables v4) in development for this dll.

So I ask so - how to open the table v3 when you use the DBISAM engine v4
without any error message and table upgrade?

--
With best regards, Mike Shkolnik
EMail: mshkolnik@scalabium.com
http://www.scalabium.com

"Chris Holland" <mail@chrisholland.me.uk> wrote in message
news:63FF2DC4-5A7B-4C06-8DB7-9E51CDF9148F@news.elevatesoft.com...
> Hi Mike,
>
> What he means is that the ADO provider can connect to either a version 3
> or a Version 4 DBISAM server.
>
> You have to specify which when you setup the connection string.
>
> Chris Holland
>
>
> Mike Shkolnik wrote:
> > Michael,
> >
> >> currently we support 3 & 4.
> > How did you implement this feature?
> > I mean how you can open the table from v3 with engine v4 (without table
> > upgrade from v3 to 4)?
> >
> > --
> > With best regards, Mike Shkolnik
> > EMail: mshkolnik@scalabium.com
> > http://www.scalabium.com
> >
> >

Hi Mike,

We didn't use dbisam engine for .Net dll - it's pure
tcp/ip socket and we just implemented the protocol.
IOW, we only provide C/S way of accessing a database.

The dll is pure C# and doesn't have ANY unmanaged code,
so we couldn't use any dbisam packages even if we wanted.
We also have Compact Framework version, which makes it
even more restricted.

Regards,
Michael


Mike Shkolnik wrote:
> Chris,
>
> I understood. But how Michael implemented this feature?
>
> As I see, he used the DBISAM engine (v4 as I see because he can open the
> tables v4) in development for this dll.
>
> So I ask so - how to open the table v3 when you use the DBISAM engine v4
> without any error message and table upgrade?
>
> --
> With best regards, Mike Shkolnik
> EMail: mshkolnik@scalabium.com
> http://www.scalabium.com
>
> "Chris Holland" <mail@chrisholland.me.uk> wrote in message
> news:63FF2DC4-5A7B-4C06-8DB7-9E51CDF9148F@news.elevatesoft.com...
>
>>Hi Mike,
>>
>>What he means is that the ADO provider can connect to either a version 3
>>or a Version 4 DBISAM server.
>>
>>You have to specify which when you setup the connection string.
>>
>>Chris Holland
>>
>>
>>Mike Shkolnik wrote:
>>
>>>Michael,
>>>
>>>
>>>>currently we support 3 & 4.
>>>
>>>How did you implement this feature?
>>>I mean how you can open the table from v3 with engine v4 (without table
>>>upgrade from v3 to 4)?
>>>
>>>--
>>>With best regards, Mike Shkolnik
>>>EMail: mshkolnik@scalabium.com
>>>http://www.scalabium.com
>>>
>>>
>
>
>

Ok, I understand now. Thanks!

--
With best regards, Mike Shkolnik
E-mail: mshkolnik@scalabium.com
WEB: http://www.scalabium.com

"Michael Baytalsky" <mike@contextsoft.com> wrote in message
news:B459B3B7-F987-45AE-A1C3-E6EE57F50D7D@news.elevatesoft.com...
> Hi Mike,
>
> We didn't use dbisam engine for .Net dll - it's pure
> tcp/ip socket and we just implemented the protocol.
> IOW, we only provide C/S way of accessing a database.
>
> The dll is pure C# and doesn't have ANY unmanaged code,
> so we couldn't use any dbisam packages even if we wanted.
> We also have Compact Framework version, which makes it
> even more restricted.
>
> Regards,
> Michael
>
>
> Mike Shkolnik wrote:
> > Chris,
> >
> > I understood. But how Michael implemented this feature?
> >
> > As I see, he used the DBISAM engine (v4 as I see because he can open the
> > tables v4) in development for this dll.
> >
> > So I ask so - how to open the table v3 when you use the DBISAM engine v4
> > without any error message and table upgrade?
> >
> > --
> > With best regards, Mike Shkolnik
> > EMail: mshkolnik@scalabium.com
> > http://www.scalabium.com
> >
> > "Chris Holland" <mail@chrisholland.me.uk> wrote in message
> > news:63FF2DC4-5A7B-4C06-8DB7-9E51CDF9148F@news.elevatesoft.com...
> >
> >>Hi Mike,
> >>
> >>What he means is that the ADO provider can connect to either a version 3
> >>or a Version 4 DBISAM server.
> >>
> >>You have to specify which when you setup the connection string.
> >>
> >>Chris Holland
> >>
> >>
> >>Mike Shkolnik wrote:
> >>
> >>>Michael,
> >>>
> >>>
> >>>>currently we support 3 & 4.
> >>>
> >>>How did you implement this feature?
> >>>I mean how you can open the table from v3 with engine v4 (without table
> >>>upgrade from v3 to 4)?
> >>>
> >>>--
> >>>With best regards, Mike Shkolnik
> >>>EMail: mshkolnik@scalabium.com
> >>>http://www.scalabium.com
> >>>
> >>>
> >
> >
> >