Difference between revisions of "MS Access"

From Lazarus wiki
(Create access databases programmatically)
m (Unix/Linux: Change mdbtools link to current location)
 
(17 intermediate revisions by 7 users not shown)
Line 1: Line 1:
This page explains how to use a '''Microsoft Access''' database using [[ODBCConn|ODBC]] and FPC's built-in SQLDB. It is limited to Windows (or perhaps the Wine layer running on *nix).
+
{{MS Access}}
 +
 
 +
{{Infobox databases}}
 +
This page explains how to use a '''Microsoft Access''' database using [[ODBCConn|ODBC]] and FPC's built-in SQLDB.
  
{{Database Programming}}
 
  
 
==MS Access specifics==
 
==MS Access specifics==
  
 
===UsePrimaryKeyAsKey===
 
===UsePrimaryKeyAsKey===
 +
 
In the '''TSQLQuery''' properties, you may need to set
 
In the '''TSQLQuery''' properties, you may need to set
 
Set UsePrimaryKeyAsKey: False
 
Set UsePrimaryKeyAsKey: False
''November 2012: to do: verify if this is needed''
 
  
 
===Get just-inserted autonumber primary key===
 
===Get just-inserted autonumber primary key===
 +
 
After inserting data, Access 2000 and higher supports getting the just-inserted autonumber primary key using this query:
 
After inserting data, Access 2000 and higher supports getting the just-inserted autonumber primary key using this query:
 +
 
<syntaxhighlight lang="SQL">
 
<syntaxhighlight lang="SQL">
 
SELECT @@IDENTITY
 
SELECT @@IDENTITY
Line 17: Line 21:
  
 
=== ODBC drivers ===
 
=== ODBC drivers ===
 +
 +
==== Windows ====
 +
 
There are 2 different [[ODBCConn|ODBC]] drivers for Microsoft Access:
 
There are 2 different [[ODBCConn|ODBC]] drivers for Microsoft Access:
 
* the old driver that can only use .mdb format files, driver name is "Microsoft Access Driver (*.mdb)". Included in many Windows versions (since Windows 2000 up to and including Vista?); downloadable for older Windows versions as part of the MDAC components or Jet components. 32 bit only.
 
* the old driver that can only use .mdb format files, driver name is "Microsoft Access Driver (*.mdb)". Included in many Windows versions (since Windows 2000 up to and including Vista?); downloadable for older Windows versions as part of the MDAC components or Jet components. 32 bit only.
 
* the new driver that can access both .mdb and .accdb files, driver name is "Microsoft Access Driver (*.mdb, *.accdb)". Downloadable as the "Microsoft Access Database Engine 2010 Redistributable"; available as 32 and 64 bit.
 
* the new driver that can access both .mdb and .accdb files, driver name is "Microsoft Access Driver (*.mdb, *.accdb)". Downloadable as the "Microsoft Access Database Engine 2010 Redistributable"; available as 32 and 64 bit.
 
As usual, when using 32 bit Lazarus/FPC, use 32 bit ODBC drivers. When using 64 bit Lazarus/FPC, use 64 bit ODBC drivers.
 
As usual, when using 32 bit Lazarus/FPC, use 32 bit ODBC drivers. When using 64 bit Lazarus/FPC, use 64 bit ODBC drivers.
 +
 +
==== Unix/Linux ====
 +
 +
The [https://github.com/mdbtools/mdbtools mdbtools project] offers limited support for MS Accesss. It includes an ODBC driver which might be used. Try installing packages like mdbtools mdbtools-dev mdbtools-gmdb
 +
 +
At least on Debian, the ODBC driver name is "MDBTools".
  
 
==File-based DSN Instructions==
 
==File-based DSN Instructions==
 +
 
A file DSN is simply where the connection settings are written to a file. The reason for having a file DSN is if you want to distribute a data source connection to multiple users on different systems without having to configure a DSN for each system. For instance, I can create a file DSN to a reporting database on my desktop. I can then send the file to my users. My users can save the file DSN to their hard drives and then point their reporting applications at the file DSN.
 
A file DSN is simply where the connection settings are written to a file. The reason for having a file DSN is if you want to distribute a data source connection to multiple users on different systems without having to configure a DSN for each system. For instance, I can create a file DSN to a reporting database on my desktop. I can then send the file to my users. My users can save the file DSN to their hard drives and then point their reporting applications at the file DSN.
  
Line 28: Line 42:
  
 
=== Set up the File DSN ===
 
=== Set up the File DSN ===
 +
 
* Go to your [Data sources (ODBC)] at the control panel administrative  tools.
 
* Go to your [Data sources (ODBC)] at the control panel administrative  tools.
 
* Go to [File DSN] tab menu, Click Add, then Select <microsoft access driver>.
 
* Go to [File DSN] tab menu, Click Add, then Select <microsoft access driver>.
Line 34: Line 49:
  
 
==== File DSN contents ====
 
==== File DSN contents ====
 +
 
For reference, a file DSN that refers to an MS Access database '''may''' look something '''like''' this:
 
For reference, a file DSN that refers to an MS Access database '''may''' look something '''like''' this:
 +
 
<syntaxhighlight lang="DOS">
 
<syntaxhighlight lang="DOS">
 
[ODBC]
 
[ODBC]
Line 52: Line 69:
  
 
=== Configure your project to use file-based DSN ===
 
=== Configure your project to use file-based DSN ===
 +
 +
 
Usage of grids and other data bound controls is the same as for any other SQLDB connector, so that is not covered here.
 
Usage of grids and other data bound controls is the same as for any other SQLDB connector, so that is not covered here.
  
Line 57: Line 76:
  
 
TOBDCConnection Properties:
 
TOBDCConnection Properties:
 +
 
FileDSN: the path+filename to the DSN file saved earlier, e.g. c:\mylazarus\project1\myFile.dsn
 
FileDSN: the path+filename to the DSN file saved earlier, e.g. c:\mylazarus\project1\myFile.dsn
 
Username: admin (or whatever username you need if you are using Access security) ''this parameter may not be needed if no MS Access security is used''
 
Username: admin (or whatever username you need if you are using Access security) ''this parameter may not be needed if no MS Access security is used''
Line 63: Line 83:
  
 
== System/User DSN ==
 
== System/User DSN ==
 +
 
As explained in the [[ODBCConn|ODBC]] article, you can also use system or user DSNs, where connection settings are defined in the ODBC control panel instead of stored in a file.
 
As explained in the [[ODBCConn|ODBC]] article, you can also use system or user DSNs, where connection settings are defined in the ODBC control panel instead of stored in a file.
  
Line 69: Line 90:
  
 
== DSN-less connection ==
 
== DSN-less connection ==
 +
 
As explained in the [[ODBCConn|ODBC]] article, you can also create a DSN-less connection to your Access database where you can specify all connection parameters in code, something like:
 
As explained in the [[ODBCConn|ODBC]] article, you can also create a DSN-less connection to your Access database where you can specify all connection parameters in code, something like:
<syntaxhighlight>
+
 
 +
<syntaxhighlight lang=pascal>
 
   //Notice we're using the new MS Access driver, we could probably use the old one too:
 
   //Notice we're using the new MS Access driver, we could probably use the old one too:
 
   conn.Driver:='Microsoft Access Driver (*.mdb, *.accdb)';
 
   conn.Driver:='Microsoft Access Driver (*.mdb, *.accdb)';
Line 77: Line 100:
 
</syntaxhighlight>
 
</syntaxhighlight>
  
 +
Here is an example how to query a table in an Access mdb file using TODBCConnection, TSQLTransaction and TSQLQuery (the mdb file exists in the same folder as the project binary):
 +
 +
<syntaxhighlight lang=pascal>
 +
procedure TForm1.Button1Click(Sender: TObject);
 +
begin
 +
  //connection
 +
  ODBCConnection1.Driver := 'Microsoft Access Driver (*.mdb, *.accdb)';
 +
  ODBCConnection1.Params.Add('DBQ=.\test.mdb');      // or specify full path to mdb file
 +
  ODBCConnection1.Params.Add('Locale Identifier=1031');
 +
  ODBCConnection1.Params.Add('ExtendedAnsiSQL=1');
 +
  ODBCConnection1.Params.Add('CHARSET=ansi');
 +
  ODBCConnection1.Connected := True;
 +
  ODBCConnection1.KeepConnection := True;
 +
   
 +
  //transaction
 +
  SQLTransaction1.DataBase := ODBCConnection1;
 +
  SQLTransaction1.Action := caCommit;
 +
  SQLTransaction1.Active := True;
 +
   
 +
  SQLQuery1.DataBase := ODBCConnection1;
 +
  SQLQuery1.UsePrimaryKeyAsKey := False;
 +
  SQLQuery1.SQL.Text := 'select * from Customers';
 +
  SQLQuery1.Open;
 +
end;
 +
</syntaxhighlight>
  
 
== Example code ==
 
== Example code ==
  
 
=== Lazarus: data bound controls on forms ===
 
=== Lazarus: data bound controls on forms ===
 +
 
Working Source code sample:(Updated2_with_add_delete_update)
 
Working Source code sample:(Updated2_with_add_delete_update)
http://www.mediafire.com/file/ne1jx3zpnwzefq3/msaccesstest2.zip
+
http://www.mediafire.com/file/ne1jx3zpnwzefq3/msaccesstest2.zip ''[Dead link - November 2020]''
  
<syntaxhighlight>
+
<syntaxhighlight lang=pascal>
 
unit Unit1;  
 
unit Unit1;  
  
Line 143: Line 192:
 
   SQLTransaction1.Action := caCommit;
 
   SQLTransaction1.Action := caCommit;
 
   SQLTransaction1.Active := True; //not applied to ms access(false)
 
   SQLTransaction1.Active := True; //not applied to ms access(false)
  //SQLTransaction1.StartTransaction; //removed ONLY for lazarus-0.9.30.0-fcl-2.4.2
 
  
 
   SQLQuery1.DataBase := ODBCConnection1;
 
   SQLQuery1.DataBase := ODBCConnection1;
Line 150: Line 198:
 
   SQLQuery1.SQL.Text := 'select * from table1';
 
   SQLQuery1.SQL.Text := 'select * from table1';
  
 
+
   // :id is the parameter for the field name id
 
 
  //T.H.I.S  SQL String implementation is (ONLY) for MS_ACCESS
 
   //:id is the fieldname id
 
 
   SQLQuery1.deleteSQL.Text := 'delete from table1 where id=:id';
 
   SQLQuery1.deleteSQL.Text := 'delete from table1 where id=:id';
   //:name is the fieldname name
+
   //:name is the parameter for the field name name
 
   SQLQuery1.updateSQL.Text := 'update table1 set name=:name where id=:id';
 
   SQLQuery1.updateSQL.Text := 'update table1 set name=:name where id=:id';
 
 
  
 
   DataSource1.DataSet := SQLQuery1;
 
   DataSource1.DataSet := SQLQuery1;
Line 216: Line 259:
 
procedure TForm1.Button1Click(Sender: TObject);
 
procedure TForm1.Button1Click(Sender: TObject);
 
begin
 
begin
PrintDbGrid(DBGrid1);
+
  PrintDbGrid(DBGrid1);
 
end;
 
end;
  
Line 254: Line 297:
 
   SQLQuery1.ApplyUpdates;
 
   SQLQuery1.ApplyUpdates;
  
   '//REMOVED or ADD this 2 lines if there is a problem in your SQLdB
+
   //REMOVED or ADD this 2 lines if there is a problem in your SQLdB
   '//THIS 2 lines are =**BUG**= of SQLdB for MS_Access dataBase'
+
   //THESE 2 lines apparently work around a bug in SQLdB for MS_Access dataBase'
 +
  //**** missing reference to bugtracker item; please create a bugtracker item
 
   //SQLQuery1.Close;
 
   //SQLQuery1.Close;
 
   //SQLQuery1.Open;
 
   //SQLQuery1.Open;
  '//We don't need this 2 line's in other data models, like mySQL, sqLiTE, etc.,...'
 
  
  
Line 269: Line 312:
 
   if SQLQuery1.RecordCount>0 then
 
   if SQLQuery1.RecordCount>0 then
 
   begin
 
   begin
  SQLQuery1.Edit;
+
    SQLQuery1.Edit;
  SQLQuery1.Post;
+
    SQLQuery1.Post;
  Sqlquery1.ApplyUpdates;
+
    Sqlquery1.ApplyUpdates;
  Form1.caption := 'UPDATED';
+
    Form1.caption := 'UPDATED';
  end;
+
  end;
 
end;
 
end;
  
 
procedure TForm1.FormCloseQuery(Sender: TObject; var CanClose: boolean);
 
procedure TForm1.FormCloseQuery(Sender: TObject; var CanClose: boolean);
 
begin
 
begin
    SQLQuery1.Close;
+
  SQLQuery1.Close;
    CanClose := True;
+
  CanClose := True;
 
end;
 
end;
  
Line 289: Line 332:
  
 
=== Create a database programmatically ===
 
=== Create a database programmatically ===
 +
 
Using either ODBC driver, you can programmatically create Microsoft Access databases.
 
Using either ODBC driver, you can programmatically create Microsoft Access databases.
 +
(Note: error handling has not been tested; please update page if you tested it)
  
 
Example program:
 
Example program:
<syntaxhighlight>
+
 
 +
<syntaxhighlight lang=pascal>
 
program CreateAccessDb;
 
program CreateAccessDb;
  
Line 302: Line 348:
 
   {$ENDIF}{$ENDIF}
 
   {$ENDIF}{$ENDIF}
 
   Classes, sysutils,
 
   Classes, sysutils,
   Windows;
+
   LCLType;
  
 
Const
 
Const
Line 363: Line 409:
 
   write(CreateAccessDatabase('d:\cop\t\bla.mdb'));
 
   write(CreateAccessDatabase('d:\cop\t\bla.mdb'));
 
end.
 
end.
 +
</syntaxhighlight>
 +
 +
=== Character set issues ===
 +
 +
Old Access databases are encoded using an ANSI character set (I don't know about new ones - they probably use wide strings). Therefore, non-ASCII characters are not displayed correctly in a DBGrid or other data-aware controls. This can be fixed by attaching handlers to the OnGetText and OnSetText events of the dataset after opening:
 +
 +
<syntaxhighlight lang=pascal>
 +
uses
 +
  lconvencoding;
 +
 +
procedure TForm1.SQLQuery1AfterOpen(DataSet: TDataSet);
 +
var
 +
  i: Integer; 
 +
begin
 +
  for i:=0 to DataSet.Fields.Count-1 do
 +
  begin
 +
    if DataSet.Fields[i].DataType=ftString then
 +
    begin
 +
      DataSet.Fields[i].OnGetText := @ConvertFromDB;
 +
      DataSet.Fields[i].OnSetText := @ConvertToDB;
 +
    end;
 +
  end;
 +
end;
 +
 +
procedure TForm1.ConvertFromDB(Sender: TField; var aText: string; DisplayText: Boolean);
 +
begin
 +
  if not Sender.IsNull then
 +
    aText := WinCPToUTF8(Sender.AsString);  // if encoded in windows default code page
 +
end;
 +
 +
procedure TForm1.ConvertToDB(Sender: TField; const aText: string);
 +
begin
 +
  if aText <> '' then
 +
    Sender.Value := UTF8ToWinCP(aText);
 +
end;
 
</syntaxhighlight>
 
</syntaxhighlight>
  
Line 369: Line 450:
  
 
If you only have the Access Runtime installed, you can use this alternative database from the Mondial project as a test database:
 
If you only have the Access Runtime installed, you can use this alternative database from the Mondial project as a test database:
[http://databases.about.com/od/sampleaccessdatabases/a/Microsoft-Access-Sample-Database-Countries-Cities-And-Provinces.htm]
+
[http://databases.about.com/od/sampleaccessdatabases/a/Microsoft-Access-Sample-Database-Countries-Cities-And-Provinces.htm] ''[Dead link - November 2020]''
  
 
== See also ==
 
== See also ==
 +
 
* [[ODBCConn]] The ODBC connector this article uses
 
* [[ODBCConn]] The ODBC connector this article uses
 
[[Category:Databases]]
 
[[Category:FPC]]
 

Latest revision as of 08:28, 15 November 2020

English (en) español (es) français (fr) русский (ru)

Databases portal

References:

Tutorials/practical articles:

Databases

Advantage - MySQL - MSSQL - Postgres - Interbase - Firebird - Oracle - ODBC - Paradox - SQLite - dBASE - MS Access - Zeos

This page explains how to use a Microsoft Access database using ODBC and FPC's built-in SQLDB.


MS Access specifics

UsePrimaryKeyAsKey

In the TSQLQuery properties, you may need to set Set UsePrimaryKeyAsKey: False

Get just-inserted autonumber primary key

After inserting data, Access 2000 and higher supports getting the just-inserted autonumber primary key using this query:

SELECT @@IDENTITY

ODBC drivers

Windows

There are 2 different ODBC drivers for Microsoft Access:

  • the old driver that can only use .mdb format files, driver name is "Microsoft Access Driver (*.mdb)". Included in many Windows versions (since Windows 2000 up to and including Vista?); downloadable for older Windows versions as part of the MDAC components or Jet components. 32 bit only.
  • the new driver that can access both .mdb and .accdb files, driver name is "Microsoft Access Driver (*.mdb, *.accdb)". Downloadable as the "Microsoft Access Database Engine 2010 Redistributable"; available as 32 and 64 bit.

As usual, when using 32 bit Lazarus/FPC, use 32 bit ODBC drivers. When using 64 bit Lazarus/FPC, use 64 bit ODBC drivers.

Unix/Linux

The mdbtools project offers limited support for MS Accesss. It includes an ODBC driver which might be used. Try installing packages like mdbtools mdbtools-dev mdbtools-gmdb

At least on Debian, the ODBC driver name is "MDBTools".

File-based DSN Instructions

A file DSN is simply where the connection settings are written to a file. The reason for having a file DSN is if you want to distribute a data source connection to multiple users on different systems without having to configure a DSN for each system. For instance, I can create a file DSN to a reporting database on my desktop. I can then send the file to my users. My users can save the file DSN to their hard drives and then point their reporting applications at the file DSN.

If you want to use a file-based DSN with the SQLDB ODBC driver:

Set up the File DSN

  • Go to your [Data sources (ODBC)] at the control panel administrative tools.
  • Go to [File DSN] tab menu, Click Add, then Select <microsoft access driver>.
  • Next, browse to your current Lazarus project path to save your .DSN file, because that dsn file will contain the configuration needed to access your database file (.mdb).
  • Click Next, then Finish (you now have created a new .dsn file) of which will be use in your TODBCConnection [FileDSN].

File DSN contents

For reference, a file DSN that refers to an MS Access database may look something like this:

[ODBC]
DRIVER=Microsoft Access Driver (*.mdb)
UID=admin
UserCommitSync=Yes
Threads=3
SafeTransactions=0
PageTimeout=5
MaxScanRows=8
MaxBufferSize=2048
FIL=MS Access
DriverId=25
DefaultDir=
DBQ=YOUR_msaccess.mdb

Configure your project to use file-based DSN

Usage of grids and other data bound controls is the same as for any other SQLDB connector, so that is not covered here.

As you're using an ODBC connection, you should have a TODBCConnection object.

TOBDCConnection Properties:

FileDSN: the path+filename to the DSN file saved earlier, e.g. c:\mylazarus\project1\myFile.dsn Username: admin (or whatever username you need if you are using Access security) this parameter may not be needed if no MS Access security is used Do not put any other entries in the properties.


System/User DSN

As explained in the ODBC article, you can also use system or user DSNs, where connection settings are defined in the ODBC control panel instead of stored in a file.

The TODBCConnection should have DatabaseName: <name_of_your_DSN>

DSN-less connection

As explained in the ODBC article, you can also create a DSN-less connection to your Access database where you can specify all connection parameters in code, something like:

  //Notice we're using the new MS Access driver, we could probably use the old one too:
  conn.Driver:='Microsoft Access Driver (*.mdb, *.accdb)';
  conn.Params.Add('DBQ=c:\somedirectory\test.mdb');
  ... add whatever parameters you want/need...

Here is an example how to query a table in an Access mdb file using TODBCConnection, TSQLTransaction and TSQLQuery (the mdb file exists in the same folder as the project binary):

procedure TForm1.Button1Click(Sender: TObject);
begin
  //connection
  ODBCConnection1.Driver := 'Microsoft Access Driver (*.mdb, *.accdb)';
  ODBCConnection1.Params.Add('DBQ=.\test.mdb');      // or specify full path to mdb file
  ODBCConnection1.Params.Add('Locale Identifier=1031');
  ODBCConnection1.Params.Add('ExtendedAnsiSQL=1');
  ODBCConnection1.Params.Add('CHARSET=ansi');
  ODBCConnection1.Connected := True;
  ODBCConnection1.KeepConnection := True;
     
  //transaction
  SQLTransaction1.DataBase := ODBCConnection1;
  SQLTransaction1.Action := caCommit;
  SQLTransaction1.Active := True;
     
  SQLQuery1.DataBase := ODBCConnection1;
  SQLQuery1.UsePrimaryKeyAsKey := False;
  SQLQuery1.SQL.Text := 'select * from Customers';
  SQLQuery1.Open;
end;

Example code

Lazarus: data bound controls on forms

Working Source code sample:(Updated2_with_add_delete_update) http://www.mediafire.com/file/ne1jx3zpnwzefq3/msaccesstest2.zip [Dead link - November 2020]

unit Unit1; 

{$mode objfpc}{$H+}

interface

uses
  Classes, SysUtils, odbcconn, sqldb, db, FileUtil, LResources, Forms, Controls,
  Graphics, Dialogs, DBGrids, DbCtrls, StdCtrls, Printers, PrintersDlgs;

type

  { TForm1 }

  TForm1 = class(TForm)
    Button1: TButton;
    Button2: TButton;
    Button3: TButton;
    Button4: TButton;
    Datasource1: TDatasource;
    DBEdit1: TDBEdit;
    DBEdit2: TDBEdit;
    DBGrid1: TDBGrid;
    ODBCConnection1: TODBCConnection;
    PrintDialog1: TPrintDialog;
    SQLQuery1: TSQLQuery;
    SQLTransaction1: TSQLTransaction;
    procedure Button1Click(Sender: TObject);
    procedure Button2Click(Sender: TObject);
    procedure Button3Click(Sender: TObject);
    procedure Button4Click(Sender: TObject);
    procedure FormCloseQuery(Sender: TObject; var CanClose: boolean);
    procedure FormShow(Sender: TObject);
  private
    { private declarations }
    procedure PrintDbGrid(dbGrid:TdbGrid);
  public
    { public declarations }
  end; 

var
  Form1: TForm1; 

implementation

{ TForm1 }

procedure TForm1.FormShow(Sender: TObject);
begin
  //connection
  ODBCConnection1.FileDSN := ExtractFilePath(Application.ExeName) + 'file.dsn';
  ODBCConnection1.Connected := True;
  ODBCConnection1.KeepConnection := True;

  //transaction
  SQLTransaction1.DataBase := ODBCConnection1;
  SQLTransaction1.Action := caCommit;
  SQLTransaction1.Active := True; //not applied to ms access(false)

  SQLQuery1.DataBase := ODBCConnection1;
  SQLQuery1.UsePrimaryKeyAsKey := False;

  SQLQuery1.SQL.Text := 'select * from table1';

  // :id is the parameter for the field name id
  SQLQuery1.deleteSQL.Text := 'delete from table1 where id=:id';
  //:name is the parameter for the field name name
  SQLQuery1.updateSQL.Text := 'update table1 set name=:name where id=:id';

  DataSource1.DataSet := SQLQuery1;
  DBGrid1.DataSource := DataSource1;
  DBGrid1.ReadOnly := true;

  DBEdit1.DataField := 'id';
  DBEdit1.DataSource := DataSource1;
  DBEdit2.DataField := 'name';
  DBEdit2.DataSource := DataSource1;

  SQLQuery1.Open;
end;

function MulDiv(nNumber, nNumerator, nDenominator: Integer): Integer;
begin
  Result:=Round(int64(nNumber)*int64(nNumerator)/nDenominator);
end;
procedure TForm1.PrintDbGrid(dbGrid:TdbGrid);
const
  LeftMargin = 0.05;
  TopMargin = 0.05;
  BottomMargin = 0.05;
var
  i: integer;
  x,y: integer;
begin
  if PrintDialog1.Execute then
    begin
    Printer.BeginDoc;
    Printer.Canvas.Font.Size := 12;

    y := Round(TopMargin*Printer.PageHeight);
    dbGrid.DataSource.DataSet.First;
    while not dbGrid.DataSource.DataSet.Eof do
      begin
      x := Round(LeftMargin*Printer.PageWidth);
      for i := 0 to dbGrid.DataSource.DataSet.FieldCount-1 do
        begin
        printer.Canvas.TextOut(x,y,dbGrid.DataSource.DataSet.Fields[i].AsString);
        x := x + MulDiv(dbGrid.Columns[i].Width,72, dbGrid.Width);
        end;
      dbGrid.DataSource.DataSet.Next;
      y := y + printer.Canvas.TextHeight('A');
      if y > (1-TopMargin-BottomMargin)* Printer.PageHeight then
        begin
        y := Round(TopMargin*Printer.PageHeight);
        Printer.NewPage;
        end;
      end;
    Printer.EndDoc;
    end
    else
    Form1.caption := 'NO PRINTER INSTALLED';
end;

procedure TForm1.Button1Click(Sender: TObject);
begin
  PrintDbGrid(DBGrid1);
end;

procedure TForm1.Button2Click(Sender: TObject);
begin
if button2.Caption = 'new' then
begin
  SQLQuery1.Insert;
  button2.Caption := 'save';
  exit
  end
  else
  begin
    if (dbedit1.Text = '') or (dbedit2.Text = '')
    then
    begin
    SQLQuery1.Cancel;
    end
    else
    begin
    if SQLQuery1.State = dsInsert then
       begin
       SQLQuery1.Post;
       SQLQuery1.ApplyUpdates;
       Form1.caption := 'ADDED';
       end;
    end;
  end;
button2.Caption := 'new';
end;

procedure TForm1.Button3Click(Sender: TObject);
begin
if SQLQuery1.RecordCount>0 then
  begin
  SQLQuery1.Delete;
  SQLQuery1.ApplyUpdates;

  //REMOVED or ADD this 2 lines if there is a problem in your SQLdB
  //THESE 2 lines apparently work around a bug in SQLdB for MS_Access dataBase'
  //**** missing reference to bugtracker item; please create a bugtracker item
  //SQLQuery1.Close;
  //SQLQuery1.Open;


  Form1.caption := 'DELETED';
  end;
end;

procedure TForm1.Button4Click(Sender: TObject);
begin
  if SQLQuery1.RecordCount>0 then
  begin
    SQLQuery1.Edit;
    SQLQuery1.Post;
    Sqlquery1.ApplyUpdates;
    Form1.caption := 'UPDATED';
  end;
end;

procedure TForm1.FormCloseQuery(Sender: TObject; var CanClose: boolean);
begin
  SQLQuery1.Close;
  CanClose := True;
end;

initialization
  {$I unit1.lrs}

end.

Create a database programmatically

Using either ODBC driver, you can programmatically create Microsoft Access databases. (Note: error handling has not been tested; please update page if you tested it)

Example program:

program CreateAccessDb;

{$mode objfpc}{$H+}

uses
  {$IFDEF UNIX}{$IFDEF UseCThreads}
  cthreads,
  {$ENDIF}{$ENDIF}
  Classes, sysutils,
  LCLType;

Const
   ODBC_ADD_DSN=1;
   ODBC_CONFIG_DSN=2;
   ODBC_REMOVE_DSN=3;
   ODBC_ADD_SYS_DSN=4;
   ODBC_CONFIG_SYS_DSN=5;
   ODBC_REMOVE_SYS_DSN=6;
   ODBC_REMOVE_DEFAULT_DSN=7;
function SQLConfigDataSource(hwndParent: Integer; fRequest: Integer;
  lpszDriverString: PChar; lpszAttributes: PChar): Integer; stdcall; external 'odbccp32.dll';
function SQLInstallerError(iError: integer; pfErrorCode: PInteger; lpszErrorMsg: string; cbErrorMsgMax: integer; pcbErrorMsg: PInteger): integer; stdcall; external 'odbccp32.dll';

function CreateAccessDatabase(DatabaseFile: string): boolean;
var
  DBPChar: PChar;
  Driver: PChar;
  ErrorCode, ResizeErrorMessage: integer;
  ErrorMessage: PChar;
  retCode: integer;
begin
	driver := 'Microsoft Access Driver (*.mdb, *.accdb)';
  { With this driver,
  CREATE_DB/CREATE_DBV12 will create an .accdb format database;
  CREATE_DBV4 will create an mdb
  http://stackoverflow.com/questions/9205633/how-do-i-specify-the-odbc-access-driver-format-when-creating-the-database
  }
  DBPChar:=PChar('CREATE_DBV4="'+DatabaseFile+'"');
  retCode := SQLConfigDataSource(Hwnd(nil), ODBC_ADD_DSN, Driver, DBPChar);
  if retCode<>0 then
  begin
    //try alternate driver
    Driver := 'Microsoft Access Driver (*.mdb)';
    DBPChar:=PChar('CREATE_DB="'+DatabaseFile+'"');
    retCode := SQLConfigDataSource(Hwnd(nil), ODBC_ADD_DSN, Driver, DBPChar);
  end;
  if retCode=0 then
  begin
    result:=true;
  end
  else
  begin
    result:=false;
    ErrorCode:=0;
    ResizeErrorMessage:=0;
    // todo: verify how the DLL is called - use pointers?; has not been tested.
    GetMem(ErrorMessage,512);
    try
      SQLInstallerError(1, @ErrorCode, ErrorMessage, SizeOf(ErrorMessage), @ResizeErrorMessage);
    finally
      FreeMem(ErrorMessage);
    end;
    raise Exception.CreateFmt('Error creating Access database: %s', [ErrorMessage]);
  end;
end;

begin
  writeln('Result: ');
  write(CreateAccessDatabase('d:\cop\t\bla.mdb'));
end.

Character set issues

Old Access databases are encoded using an ANSI character set (I don't know about new ones - they probably use wide strings). Therefore, non-ASCII characters are not displayed correctly in a DBGrid or other data-aware controls. This can be fixed by attaching handlers to the OnGetText and OnSetText events of the dataset after opening:

uses
  lconvencoding;
 
procedure TForm1.SQLQuery1AfterOpen(DataSet: TDataSet);
var
  i: Integer;  
begin
  for i:=0 to DataSet.Fields.Count-1 do
  begin
    if DataSet.Fields[i].DataType=ftString then
    begin
      DataSet.Fields[i].OnGetText := @ConvertFromDB;
      DataSet.Fields[i].OnSetText := @ConvertToDB;
    end;
  end;
end;
 
procedure TForm1.ConvertFromDB(Sender: TField; var aText: string; DisplayText: Boolean);
begin
  if not Sender.IsNull then
    aText := WinCPToUTF8(Sender.AsString);  // if encoded in windows default code page
end;
 
procedure TForm1.ConvertToDB(Sender: TField; const aText: string);
begin
  if aText <> '' then 
    Sender.Value := UTF8ToWinCP(aText);
end;

Example database

Microsoft Access ships with the Northwind example database.

If you only have the Access Runtime installed, you can use this alternative database from the Mondial project as a test database: [1] [Dead link - November 2020]

See also

  • ODBCConn The ODBC connector this article uses