Hi Tim,

Just wanted to say THANK YOU so much for DBISam. I know I've been working
with it for a number of years now, but days like today, where I'm sitting
back, developing an application using DBISam, I stop and ponder on how
simple and enjoyable DBISam has made my working life - and it puts a little
smile on my face.

I try not to take things for granted in life - so I try to reflect on what I
have from time to time. And (in my work life , DBISam rates high up
there!

(The boys and girls on the DBISam newsgroup rate high too. Always good for
help, a chat, or a bit of humor

If it wasn't for DBISam, I'd hate to think what I might be working with
now... (mssql crosses my mind... cold shiver <brrrrrrr>)   

Cheers

Adam.

Here here! I agree completely. I love DBISAM and recommend it to everyone.
The word I use most is RELIABILITY.

I will upgrade to ElevateDB as soon as it (and my money) is available.

I am considering the purchase of an alternate single-file database though
for writing small applications where it would be nice to have my own single
file document format or a little configuration and information file included
with my app. If there was a lightweight single file database (without SQL or
other perks) by Elevate it would have already been purchased.

-Johnnie

Johnnie,

If you write in Delphi have you considered using the ClientDataset?

Use its "save to file" option & bingo, you have a simple file that can be accessed as a
dataset.

I use it pretty often when I need basic & simple local data saving capability in addition
to DBISAM.

Adam

Adam,

<< Just wanted to say THANK YOU so much for DBISam. I know I've been working
with it for a number of years now, but days like today, where I'm sitting
back, developing an application using DBISam, I stop and ponder on how
simple and enjoyable DBISam has made my working life - and it puts a little
smile on my face. >>

You're quite welcome, and thanks for the kind words.

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:5A2FE399-D3B0-4EAD-AFAD-4270AFCFCA91@news.elevatesoft.com...

> You're quite welcome, and thanks for the kind words.

No worries Tim. My plan is to top up my account with kind words while things
are going right, so I can withdrawl some when EDB is released and I have
some bugs, but still be in the black.  

Cheers

Adam.

For applications where the user thinks they are working with a "document",
but I have chosen to implement it using a database, I hide this fact from
the user by storing my database as a backup file using the inbuilt backup
and restore facilities of DBISAM.

My user opens my software, then chooses to open a "document" file.  Behind
the scenes I then restore this file into a series of tables in a temporary
directory on disk, or to memory tables.  The user then edits his
"document" and when finished he saves it again.  Behind the scenes I back
it up to the disk file and delete the temporary files.

--Bill Sparrow--

"Bill Sparrow" <bsparrow@cix.co.uk> wrote in message
news:memo.20061101184622.2596D@bsparrow.uwclub.net...
> For applications where the user thinks they are working with a "document",
> but I have chosen to implement it using a database, I hide this fact from
> the user by storing my database as a backup file using the inbuilt backup
> and restore facilities of DBISAM.
>
> My user opens my software, then chooses to open a "document" file.  Behind
> the scenes I then restore this file into a series of tables in a temporary
> directory on disk, or to memory tables.  The user then edits his
> "document" and when finished he saves it again.  Behind the scenes I back
> it up to the disk file and delete the temporary files.

I did the same type of thing in one application. I mean *exactly* the same
thing.

-Johnnie

Bill,

Did the same thing too.. but I used an ascii text export & import
because of security issues on the user's server. I think this is a great
model for some applications & its why I have been asking for several
years to have multiple in-memory databases. If you could have separate
in-memory databases it is easy to make an app where a user could work on
2 or more database documents at the same time.

Sean

bsparrow@cix.co.uk (Bill Sparrow) wrote:
> For applications where the user thinks they are working with a "document",
> but I have chosen to implement it using a database, I hide this fact from
> the user by storing my database as a backup file using the inbuilt backup
> and restore facilities of DBISAM.
>
> My user opens my software, then chooses to open a "document" file.  Behind
> the scenes I then restore this file into a series of tables in a temporary
> directory on disk, or to memory tables.  The user then edits his
> "document" and when finished he saves it again.  Behind the scenes I back
> it up to the disk file and delete the temporary files.
>
> --Bill Sparrow--
>