Going thru the feature comparison list, I see this

(10) The table encryption in DBISAM is performed using a developer-defined
password for each table, while ElevateDB uses one engine-level password for
all tables

what does it mean?

Thanks.

Robert

Hi Robert,

I believe it means that tables in DBISam are individually encrypted. (ie, if
you want all the tables to be encrypted you have to encrypt each one, one by
one), as opposed to EDB which allows you to encrypt an entire database
without having to individually encrypt each table.

.... or so that's how I understand it.

Cheers

Adam.

"Adam H." <ahairsub5@jvxp_removeme.com> wrote in message
news:44CEC6C5-244A-4699-9B95-13BAF499FD6C@news.elevatesoft.com...
> Hi Robert,
>
> I believe it means that tables in DBISam are individually encrypted. (ie,
> if you want all the tables to be encrypted you have to encrypt each one,
> one by one), as opposed to EDB which allows you to encrypt an entire
> database without having to individually encrypt each table.
>

As long as I can still do it the DBISAM way, encrypting just one table at a
time, I'm OK with that.

Robert

Robert,

<< (10) The table encryption in DBISAM is performed using a
developer-defined password for each table, while ElevateDB uses one
engine-level password for all tables

what does it mean? >>

As you know, DBISAM used a (possibly) different password for each table that
was encrypted.   With ElevateDB, you set the password at the engine level in
code, and simply designate which tables you want encrypted.  All of the
encrypted tables are encrypted using the same password, and the whole
AddPassword, RemovePassword, etc. functionality is no longer required.  The
user security functionality was effectively separated from the disk
encryption functionality.  IOW, in ElevateDB if you want to restrict access
to a particular table, then you should use users/roles and database/table
privileges to do so, not encryption.  If you want data to be secure on disk,
then you would encrypt the tables and/or database catalog (the configuration
file is always encrypted in ElevateDB because it stores the user security
information).

--
Tim Young
Elevate Software
www.elevatesoft.com

"Tim Young [Elevate Software]" <timyoung@elevatesoft.com> wrote in message
news:8FDE8DF3-A894-482A-BF23-AEE06AE4BE32@news.elevatesoft.com...

Good job Rudy does not frequent this group,
his finger would hover on his OT button.
Double barrell question's send him crazy.
He couldnt figure the subject line
Rita