Publish date: 2008-11-09
Updated: 2018-08-22

Working with Firebird and InterBase with limited system rights.

The access to Firebird and InterBase without installation of additional components in the operating system is topical for:
  • WEB-applications on external hosting.
  • Portable-applications connected to Firebird Embedded.
  • Applications working with the database on a computer with limited user rights.

Manifest is the alternative to component registration in the system

Manifest — is XML file describing the client’s application and libraries required for its work.

Manifest can be stored both in the application resources and on the disc close the program execution module. For the application to find manifest file in the second case it shall be named: PROGRAM_NAME.exe.manifest

One can work with manifests staring from Windows XP.

Creation of manifest files for connection to Firebird and InterBase

To enable the client’s application to find unregistered driver one shall:
  • Create manifest file of the client’s application named PROGRAM_NAME.exe.manifest.
  • Indicate the link to the manifest file of IBProvider without .manifest extension in it.
  • Create IBProvider manifest file (v1, v2 or v3).
  • Indicate appropriate CLSID and ProgID from table 1 in IBProvider manifest.
 Driver   Current version   Driver file name   Manifest file name   progID   clsID 
IBProvider v1 _IBProvider.dll _IBProvider.dll.manifest LCPI.IBProvider.1 {1352C0F0-DED2-11D3-A7AC-00A0C907DB93}
_IBProvider_i.dll _IBProvider_i.dll.manifest
IBProvider v2 _IBProvider_v2.dll _IBProvider_v2.dll.manifest LCPI.IBProvider.2 {3439B9D5-23B6-4661-9F0C-5CD74B1C66CB}
_IBProvider_v2_i.dll _IBProvider_v2_i.dll.manifest
IBProvider v3 _IBProvider_v3_i.dll _IBProvider_x3_i.dll.manifest LCPI.IBProvider.3 {769A1280-04BF-11D8-AE8B-00A0C907DB93}
_IBProvider_x3_w64_i.dll _IBProvider_x3_w64_i.dll.manifest

The example of the .Net Framework client’s application manifest file PROGRAM_NAME.exe.manifest for IBProvider v3 (32bit):

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">

<assemblyIdentity name="PROGRAM_NAME_WITHOUT_EXTENSION" version="" processorArchitecture="msil"></assemblyIdentity>

            <assemblyIdentity name="_IBProvider_x3_i.dll"  version=""></assemblyIdentity>


The example of _IBProvider_x3_i.dll.manifest file:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1"

  <file name = "_IBProvider_x3_i.dll">
   <comClass progid="LCPI.IBProvider.3 " clsid="{769A1280-04BF-11D8-AE8B-00A0C907DB93}" threadingModel = "Apartment" />


Additional modules for IBProvider v3 work

IBProvider v3 work requires Microsoft Visual C++ 2005 SP1 Redistributable Package of 32-bit or 64-bit version depending on the operating system bit set.

Microsoft Visual C++ 2005 SP1 Redistributable Package contains three files:
  • msvcp80.dll
  • msvcr80.dll
  • Microsoft.VC80.CRT.manifest
You can take the files from IBProvider Professional distribution package or download from ibprovider website.

Additional modules for IBProvider v2 and IBProvider v1 work

To enable IBProvider v2 and IBProvider v1 functioning you shall copy cc3250mt.dll. library to the client’s computer. You can download it from ibprovider website.

How can i work with IBProvider without registering on Windows Vista?

This solution didn’t work on Windows Vista. Please read related topic for setup your Vista Application for access to IBProvider without registering.

Useful links

Related tags: Firebird, InterBase, web, portable applications, firebird embedded, asp, .net, odbc driver, ole db provider Firebird ODBC, InterBase ODBC, Firebird driver for ole db, InterBase Delphi, Firebird Delphi
Publish date: 2008-11-09. Copyright: IBProvider. This material may be reproduced on other web sites, without written permission but link required.