Probably way to late for anything to be done but here goes.

There's a few tables I'd like to share between two or more apps. Its easy enough to create a separate database and reference that from each app unless I want encryption and then all the databases have to share the same encryption password which since I'm giving users a facility to set their own encryption password and there will be at least two groups is possibly not going to be the case.

Having set the scene the suggestion is to move encryption down from session to database, or at least have something which gives the same effect eg a database level encryption that overrides the session level.

Roy Lambert

+1

Barry

Roy,

<< Probably way to late for anything to be done but here goes. >>

Never say never.  I'm making the remote comms encryption password more
granular in 2.16.  The encryption passwords, in general, are way too broad.

<< There's a few tables I'd like to share between two or more apps. Its easy
enough to create a separate database and reference that from each app unless
I want encryption and then all the databases have to share the same
encryption password which since I'm giving users a facility to set their own
encryption password and there will be at least two groups is possibly not
going to be the case.

Having set the scene the suggestion is to move encryption down from session
to database, or at least have something which gives the same effect eg a
database level encryption that overrides the session level. >>

I'll have to think about this further, of course, but I think it can be
done.

Tim Young
Elevate Software
www.elevatesoft.com