Is it possible to have a DBISAM database created as just one file?  I am interested in using DBISAM in local embedded (not C/S) mode with Delphi
7 and it would be useful to treat each database as a single, portable file.

If this is not possible in v4.x, will it be possible in the upcoming v5 release?

"Greg Bishop" <bishop@porpoisemedia.com> wrote in message
news:FCAAE138-0A8C-4C07-9E0A-A7566F7C4743@news.elevatesoft.com...
> Is it possible to have a DBISAM database created as just one file?  I am
> interested in using DBISAM in local embedded (not C/S) mode with Delphi
> 7 and it would be useful to treat each database as a single, portable
> file.
>
> If this is not possible in v4.x, will it be possible in the upcoming v5
> release?

It is not possible in either version to have a single file database. Version
5 will actually add one more "catalog" file to an entire database, I
understand from postings here.

There is a technique you can do (in v4) to simulate a single-file database
though - if it is a single-user application. You can just create all tables
in memory and back them up to a single compressed disk file at any time.
When it comes time to load them back, you just restore the compressed backup
file into your memory tables. I am intending to use this single-file method
for an upcoming application after getting the idea from others in these
groups.

-Johnnie

Johnnie,

<< It is not possible in either version to have a single file database.
Version 5 will actually add one more "catalog" file to an entire database, I
understand from postings here. >>

Correct.  However, the beauty part is that you only need to ship the catalog
with your application (if you want, you can also just recreate the entire
catalog from scratch using SQL) and ElevateDB will create all of the tables,
etc. as needed.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:020944AB-9681-4727-8F47-0611A0668D9F@news.elevatesoft.com...
> << It is not possible in either version to have a single file database.
> Version 5 will actually add one more "catalog" file to an entire database,
> I understand from postings here. >>
>
> Correct.  However, the beauty part is that you only need to ship the
> catalog with your application (if you want, you can also just recreate the
> entire catalog from scratch using SQL) and ElevateDB will create all of
> the tables, etc. as needed.

I look forward to reading the documentation on catalogs and any other new
things in ElevateDB. Do you need a proof-reader?

-Johnnie

Tim Young [Elevate Software] wrote <<

  Correct.  However, the beauty part is that you only need
  to ship the catalog with your application (if you want,
  you can also just recreate the entire catalog from
  scratch using SQL) and ElevateDB will create all of the
  tables, etc. as needed.
  >>

Yummy.  But if I then ship an upgrade with some new,
modified or 'missing' entries in the new catalog, what will
it have to offer then?  

Malcolm

--

Malcolm,

<< Yummy.  But if I then ship an upgrade with some new, modified or
'missing' entries in the new catalog, what will it have to offer then?  
>>

You won't want to do that, at least not initially.  You'll need to use
AlterTable, etc. to add/modify/subtract metadata elements as needed in the
existing catalog.  However, that is an interesting feature to consider
adding.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim Young [Elevate Software] wrote <<

However, that is an interesting
  feature to consider adding.

>>

I agree.  At present I use Peter Mora's component which is
roughly equivalent to using a catalog to provide Table
methods such as CompareStructure, AlterTable, MakeTable.

It may not be possible to cover everything, but a lot of
the grunt could be covered.

Malcolm
--