Re: Suggestoins for Local DB to use with Shareware
- From: "Ray Porter" <ray_porter@xxxxxxx>
- Date: Sun, 30 Apr 2006 08:59:33 -0400
I agree. I use Access for all my small installations. First, it's almost
ubiquitous so you can usually get by without installing anything at all,
other than your particular MDB file. The standard ADO components work very
well and you can usually use the same SQL statements when you scale up to a
real RDBMS. It doesn't have stored procedures but that's usually a minor
adjustment. Even if the customer doesn't have Access installed, I think the
Jet drivers are part of MDAC again so it's a quick download from MS if
they're not present. Personally, I haven't had to download anything for a
single customer yet -- they're all already had full Office (including
Access) installations.
Ray Porter
"I.P. Nichols" <nospam@xxxxxxxxxx> wrote in message
news:4454a130$1@xxxxxxxxxxxxxxxxxxxxxxxxx
"G. Bradley MacDonald" wrote
I am looking for suggestions for a good local DB for our shareware app.
The DB should fully support SQL.
It would be nice if it only had one actual file - storing all the
tables/indexes, etc in that one file.
I would choose MS Access...
It must be able to handle string fields of up to 512 characters in size.
Larger would be nice. It would even be better if it they were like
VarChar fields in a relational database and only took up the size that
was used.
Yep,it has a fixed length text field (same as VarWChar) limit of 255 char
and a memo field (same as LongVarWChar) limit of 1.2MB (IIRC) and a Blob
field for binary data.
The MS Access fields correspond nicely with MS SQL fields and I once wrote
a .NET v1.1 app that used the ubiquious NorthWind database in either MS
Access or MS SQL and you could switch between database engines by merely
changing the connection string. Also the MS SQL data migration tools make
simple work of upgrading data from MS Access to MS SQL. I use the Office
version of Access to build and maintain the Access databases, any version
works just fine for that purpose.
It must have a low foot print in terms of size. This is shareware and
is downloadable. Somewhere arount 1 to 2 MB would be tollerable.
How about zero (0) foot print!
We will also be supporting MS SQL, Oracle, Interbase - for larger
customers - but want to support a local DB for smaller customers. So -
this DB must be able to support SQL as its main way of accessing the
data. It MUST be accessable using Borlands standard components - no
special TTable derivities is important.
The SQL used in MS Access meets your requirements. It also supports Views
and Procedures. Other features available from Delphi W32 is the ability to
compact and/or repair the database. And you can have a simple password
that keeps nosey folks with Access for being able to get into the
database.
IMO the MS Access database is ideal for your requirements. And it's Jet-4
provider will be available on Vista if that means anything to you...
.
- Follow-Ups:
- Re: Suggestoins for Local DB to use with Shareware
- From: I.P. Nichols
- Re: Suggestoins for Local DB to use with Shareware
- References:
- Suggestoins for Local DB to use with Shareware
- From: G . Bradley MacDonald
- Re: Suggestoins for Local DB to use with Shareware
- From: I.P. Nichols
- Suggestoins for Local DB to use with Shareware
- Prev by Date: Re: Suggestoins for Local DB to use with Shareware
- Next by Date: Re: What is the Nature of a Delphi Advocacy Group in 2006?
- Previous by thread: Re: Suggestoins for Local DB to use with Shareware
- Next by thread: Re: Suggestoins for Local DB to use with Shareware
- Index(es):
Relevant Pages
|
