Frequently Asked Questions
VistaDB 3.x Related
- Are there any runtime or deployment fees?
No. We do not charge runtime fees to embed our desktop database engine with your product.
- Can VistaDB be used with Microsoft Access to build
applications?
Technically, yes, you can use VistaDB 2.1 OLE DB. However,
supporting MS-Access is not our focus so we do not have samples on how to do
this.
- How is VistaDB licensed?
- One license is required per developer
(i.e. Per
developer licensing)
- Each licence allows the Licensee to install and use
VistaDB on an unlimited # computers and devices owned and used by the
Licensee
- The VistaDB database engine may be freely distributed
with applications that were developed using a licensed copy of VistaDB
- There are no restrictions and no royalties for deploying
the VistaDB engine
- Can a database schema be created and modified by code?
Yes. You may create and modify database schemas (i.e.
structures) via code. Both SQL commands and DDA objects may be used.
- Does VistaDB support Stored Procedures?
VistaDB 3 supports CLR Procs which let you store managed
.NET source code (C#, VB.NET) in the database, thereby providing even more
power and flexibility than Stored Procs. TSQL Stored Procs will be added in a later release (see roadmap).
- Does VistaDB support Replication?
No. This feature is planned for late 2007 release.
- Does VistaDB 3.x support the Compact Framework 2?
Yes.
- Does VistaDB support the Dot Net Framework Version 3?
Yes.
- Does VistaDB 3 support Mono?
Yes. VistaDB 3.0 ran under Mono 1.1, and VistaDB 3.3 runs under Mono 1.2 as a Dot Net 2 assembly.
Note: The Mono project is a port of the .NET Framework to
Linux sponsored by Novell.
Read more
- Can I deploy an ASP.NET application to a shared host?
Yes and VistaDB 3.x supports the Allow Partially Trusted
Callers attribute as well. We have customers using
Re-invent.com which is a
shared ASP.NET host.
- Do deployed VistaDB applications need access to the
registry, System32 folder or GAC?
No. Deployed VistaDB applications do not require access to
the registry or GAC. For .NET apps, copy the VistaDB.NETxx.DLL assembly to the
same directory as your .EXE or .DLL or use ILMerge to completely embed the
engine into your application.
- How do I migrate an Access .MDB database that is password
protected to VistaDB 3.x?
- Run the VistaDB Data Migration Wizard and start a new
MS-Access migration
- Select "[x] Custom Connection string" on step 4
- Enter the following string with the correct path info and
.MDB database name:
Provider=Microsoft.Jet.OLEDB.4.0; User
ID=Admin; Password=LoginPwd; Data Source=C:\MyData\MyDatabase.MDB;
Jet OLEDB:Database Password=MDBpassword
- Does VistaDB support 64 Bit Windows XP or Windows Vista?
Yes! Because VistaDB 3 is a managed engine it is automatically JIT'd to 64 bit under a 64 bit OS. We have also recently added support for the Server Explorer in VS 2005 while running on 64 bit Windows. VS 2005 is a 32 bit app, and runs on WoW on 64 bit platforms.
- Do you offer the source code to VistaDB?
Yes, under a specific end user license agreement.
- What are the terms of the source license?
Basically you have to agree not to release the code in any way, and not to build a database product that directly competes with us. If you want to use the Engine to build an embedded engine for a custom application that is fine. You may not build an SDK or API that is to be resold. You also may not relicense the source to anyone and agree to keep the source secure within your organization.
- What do I get with a subscription?
A subscription license provides you the following benefits:
- Unlimited priority electronic support for the duration of your subscription
- Product enchancement updates are included free
- Any new engines or add-ons to the product are included free (with the exception of the VistaDB Server which is a separate product)
- Access to development versions and patches before they become public
Please take a look at the roadmap for planned releases and features.
VistaDB 2.x Related
- Are there any runtime or deployment fees?
No.
- Can VistaDB 2.x be used with Microsoft Access to build
applications?
Technically, yes, you can use VistaDB 2.1 OLE DB. However,
supporting MS-Access is not our focus so we do not have samples on how to do
this.
- How is VistaDB licensed?
- One license is required per developer
(i.e. Per
developer licensing)
- Each licence allows the Licensee to install and use
VistaDB on an unlimited # computers and devices owned and used by the
Licensee
- The VistaDB database engine may be freely distributed
with applications that were developed using a licensed copy of VistaDB
- There are no restrictions and no royalties for deploying
the VistaDB engine
- Can a database schema be created and modified by code?
Yes. You may create and modify database schemas (i.e.
structures) via code. Both SQL commands and DDA objects may be used.
- Does VistaDB 2.x support Stored Procedures?
No.
- Does VistaDB 2.x support Replication?
No.
- Does VistaDB 2.x support the Compact Framework?
Yes, but not in embedded mode. VistaDB 2.x supports the
Compact Framework by letting connect to the VistaDB Server 2.x.
- Does VistaDB 2.x support Mono?
No.
- Can I deploy an ASP.NET application to a shared host?
Yes. We have customers using
Re-invent.com which is a
shared ASP.NET host.
- Do deployed VistaDB applications need access to the
registry, System32 folder or GAC?
No. Deployed VistaDB applications do not require access to
the registry or GAC. For .NET apps, copy the Provider and Engine to the same
directory as your EXE. For Win32 apps, copy the Engine only to the same
directory as your EXE.
- How do I migrate an Access .MDB database that is password
protected to VistaDB 2.x?
- Run the VistaDB Data Migration Wizard and start a new
MS-Access migration
- Select "[x] Custom Connection string" on step 4
- Enter the following string with the correct path info and
.MDB database name:
Provider=Microsoft.Jet.OLEDB.4.0; User
ID=Admin; Password=LoginPwd; Data Source=C:\MyData\MyDatabase.MDB;
Jet OLEDB:Database Password=MDBpassword
|