Home About Products Downloads Ordering Forum My Account

dbisam ADO.Net Provider

Overview

Package

System Req.
Screen shots
Downloads
Ordering
Request Info
Version History

Subscribe to our news


DBISAM ADO.NET PROVIDER

Package Description

DBISAM ADO.Net Provider is a .Net assembly, implementing classes and components, required by ADO.Net architecture to access DBISAM Database Server by Elevate Software.

DBISAM ADO.Net Provider supports DBISAM v3.x. and v4.x

DBISAM ADO.Net Provider communicates with DBISAM Database Server using TCP/IP protocol. It is completely programmed in C# language, which makes it fully managable. DBISAM ADO.Net Provider DOES NOT require any unmanaged dlls, ODBC drivers or COM components! It requires no configuration, except for the DbisamClient assembly has to be installed into assembly cache for use in ASP.Net applications. Morover, providing you have source code to DbiasmClient assembly, you can build it directly into your .Net executable thus eliminating all the hussle of redistributing dlls. For example of that, see simple SQLConsole utility, included in this package and also available for download separately at the download section.

DBISAM ADO.Net Provider allows connecting to DBISAM Database through DBISAM Database Server, executing SQL statements, accessing tables directly, querying table structure and more. The results of executing SQL or TableDirect Commands can be processed directly, or placed inside ADO.Net DataSet for further processing while in a disconnected state.

While in the DataSet, information can be exposed to the user, combined with other data from multiple sources, or passed remotely between tiers. Any processing performed on the data while in the DataSet can then be reconciled to DBISAM database.

Following are the main features of DBISAM ADO.Net Provider:

  • Completely written in C# and is 100% managed code.
  • DOES NOT require any unmanaged libraries, dlls or other 3rd party client libraries!
  • Uses native DBISAM protocol to access DBISAM Server via TCP/IP.
  • Supports DBISAM v3 and v4 with the same set of components.
  • Supports v4 protocol encription.
  • Provides highest performance.
  • Extremily small footprint (only about 100 KB!).
  • Easy to deploy (no dlls necessary!).
  • Supports all DBISAM data types, including BLOBs.
  • Full C# source code is available.
  • Contains reach design-time extensions, allowing to configure data adapters, commands, connections, preview real data at design-time and more.

List of Components

DbisamClient assembly includes the following components:

DbisamConnection

Establishes a connection to DBISAM Database Server and workes with transactions.

DbisamCommand

Executes SQL statements against DBISAM Database and provides access to parameters.

DbisamDataReader

Reads and exposes a forward-only stream of data from DBISAM database.

DbisamDataAdapter

Populates a DataSet from DbisamCommand and resolves the updates back into DBISAM database.

DbisamCommandBuilder

A helper object that automatically generates command properties of DbisamDataAdapter and populate the DbisamParameters collection of DbisamCommand object.

DbisamTransaction

Enables you to enlist commands executed within a transaction against DBISAM database.

DbisamParameter

Defines input parameters for the commands.

DbisamException

Exception object, thrown when an error has occured in the DBISAM Database Server. In case of an error occured at the client side, the data provider throws a .NET Framework exception.

Design-Time Features

DBISAM ADO.Net Provider design-time assembly (DbisamClient.Design.dll) contains component and property editors allowing to easy configure components on design time.
Design-time features include:

  • Connection dialog for configuring a Connection component, allowing to set connection parameters and test the connection.
  • Command configuration (in a form of a simlpe dialog), allowing to specify CommandType and CommandText, add parameters, select or create a connection, execute query and preview the result set.
  • Property editor for CommandText, allowing to select a table from a list of database tables and invoke the command configuration dialog.
  • Data Adapter configuration dialog, allowing to configure SelectCommand, automatically produce Insert/Update/Delete commands (including parameters) and specify a CommandBuilder.
  • TableMappping editor, allowing to establish mappings between the fields in a SQL result set or a database table and a table in an ADO DataSet.
  • Generator of typed DataSets produces a scheme for a DataSet based on selected DataAdapters. Use of typed DataSets can greatly simplify coding of your business logic.
  • Result Set Preview form allows to preview the data in any selected DataSet (from several DataAdapters) and test editing.
  • Component properties supplied with Description & Category parameters making them easier to understand.

Installation

In order to use DBISAM ADO.Net Provider you have to have the Microsoft.NET Framework installed on your computer and DBISAM Database Server 3.x or 4.x versions.

In order for the Microsoft .Net Framework to see DbisamClient assembly (DbisamClient.dll) it has to be added to the assembly cache.

Normally, this step will be performed by the installation program, however if you choose to do it manually, please refer to the instructions below. Adding assembly to Assembly Cache is not necessary if you place it into the same folder with the application that requires it. ASP.Net, however, in most cases will require registering the assembly.

Adding DbisamClient Assembly to the Assembly Cache

Attention! Normally you don't need to perform this step, because it has already been performed for you by the installation program. This information, however, may be usefull if you decide to produce your own distributive, including DbisamClient.dll assembly.

This operation is done by the command line utility gacutil.exe, supplied as a part of Microsoft .Net SDK. Since it is small and freely available for download, we've decided to include it into this package, to make it easier for you to locate (see in the "bin" folder).

For your convinience we included two bat files, found in the "bin" folder, that add (_GacInstall.bat) and remove (_GacRemove.bat) both run-time and design-time assemblies (DbisamClient.dll and DbisamClient.Design.dll) from assembly cache.

You can also check if the assembly is in the cache, using Microsoft .NET Framework 1.1 Configuration Console found in Administrative Tools.

Adding DbisamClient Components to the IDE

In order to be able to access an assembly from IDE the assembly should first be added to the assembly cache as described above.

Microsoft Visual Studio.Net

  1. Click on ToolBox/AddTab and specify a name for the new Tab "Dbisam.Net"
  2. Select the new tab and click pop-up menu item Add/Remove Components...
  3. Select DbisamClient.dll from .Net FrameWork Components List

Borland C# Builder

  1. Click Component/Installed .Net Components menu item
  2. Select and check mark DBISAM related components (they should appear there automatically, once the assembly is added to cache). The components, include: DbisamCommand, DbisamCommandBuilder, DbisamConnection and DbisamDataAdapter.

 Redistribution

If you're building an application, utilizing DbisamClient assembly, you will need to distribute it together with your application. In order for your appilcation to find the assembly it has to be either in the same folder with it (in case of a web application, the assembly can be put into "bin" folder within your Virtual Direoctory) or added to the GAC (Global Assembly Cache) using gacutil utility (see the explanation above).

If you have purchased the source code (available separately), you can compile DbisamClient inside your executable in which case you will not need to distribute anything at all.

If you need more information about this product, please click here to submit your request.

 

Home  | About Us  | Products  | Downloads  | Ordering  | Contact  | My Account