Download BDE database provider

SecurityLib 1.0
by
MarVic
BDE Provider
Table of contents:
INTRODUCTION........................................................................................................................................................ 1
USING PROVIDER..................................................................................................................................................... 1
Requirements.............................................................................................................................................................. 1
Two files of provider.................................................................................................................................................. 1
Connecting to provider............................................................................................................................................... 1
Other documents: ....................................................................................................................................................... 2
Introduction
This document describes the SecurityLib BDE provider, which is included in SecurityLib package.
The provider uses Borland Database Engine interface to access variety of databases. More
information about supported database systems you can find in BDE documentation.
Using provider
Requirements
The provider needs BDE version 5 or later installed on your system. You have to also setup needed
aliases and drivers. Also provider uses VCL library. There are versions of provider for versions 4 or 5 of
VCL. The Vcl4 version of provider needs VCL40.bpl, VCLDB40.bpl packages, while Vcl5 version of
provider needs VCL50.bpl, VCLDB50.bpl and VCLBDE50.bpl files. Also, the provider needs the
SecurityLib files, that is SecurityLib4.dll and SecurityAdm4.dll or SecurityLib5.dll and
SecurityAdm5.dll.
Two files of provider
The provider is divided onto two parts: the first one, contained in SecurityBDE4.dll or
SecurityBDE5.dll, supports only reading parameters and rights values. When the User Administrator
window or User window is displayed, the SecurityBDEAdm4.dll or SecurityBDEAdm5.dll is loaded.
Connecting to provider
The parameters passed to provider during initializing the Security object has following meaning:
BDEProv.doc
SecurityLib Info
1/2
•
Alias: The name of BDE alias
•
DBProvider: This provider is registered as "MarVic:BDE:Vcl4" or "MarVic:BDE:Vcl5".
Depending on the name, the right version of provider is loaded.
•
DBEng: only "BDE" value is supported by this provider
•
DBPData: The provider accepts null-terminated strings passed as this parameter. In the
string there should be options divided by commas. The options may be:
-
CachedUpdates=0 - Disables BDE cached updates mode. Some of data are
maintained on the server and not cached locally. Not all tables will be in this
mode. The Parameters, Rights and Groups tables are always cached. Default:
cached updates are on.
-
BDESQLParams=0 - This disables BDE parameter parsing. In SQL instructions
BDE catches expressions starting with : (colon) and treats them as parameters.
When this option is off, the colons are removed and the database server connected
to specific alias takes care of recognizing parameters. Some of BDE drivers (for
example direct MS Access driver) have to use this option to function properly.
Default: on.
-
RecordsetStoredProcs=1 This causes provider to use stored procedures
returning record sets. Some of the drivers (i.e. direct MS Access driver) do not
support procedures that are queries. If disabled (default), provider uses
parameterized queries instead.
The example of valid DBPData may be: "BDESQLParams = 0, RecordsetStoredProcs =
1".
Other documents:
“SecurityLib info”
Basic information and introduction.
“User’s Manual”
Information for users of programs based on SecurityLib.
“SecurityLib Administrator Manual”
Information for administrators.
“Interface and programming guide”
Information for programmers.
www.marvic.prv.pl/securitylib/
SecurityLib website.
MS Access, Windows are trademarks of Microsoft Corp.
All other trademarks are owned by their respective owners and were used only in information purposes.
BDEProv.doc
SecurityLib Info
2/2