On Friday 24 January 2003 2:04 pm, Dennis Hassell wrote:
> I can't quite tell what the problem is about sharing the database with
> new companies.
> - Is there a security issue where some records or datasets need to be
> hidden from the various companies?

My take on it was that not only are they different companies, but reside in
different COUNTRIES [he mentioned something about changing currenty notations
on some screens] [if not "reside in", then certainly "deal with" would apply]
[...]
> -----Original Message-----
[...]
> We think of dublicating all our databases into a new account (OEKVP), do
> some slight program modifications (for currency adjustments) and that
> should do the trick. Nevertheless we want to "share" 2 detail datasets
> (and their masters if necessary) from one central database among the
> different accounts.
[...]
> 1) Idea:
>
> In the new account OEKVP we create a dictionary containing database OEKV
> with all datasets except RIS-D and FREMDNR-D. And create an additional
> entry for a "fake" database OEKVX with definitions for RIS-D and
> FREMDNR-D and an open statement, which directs the program to the
> central account OEKVC.
[...]
> 2) other Ideas????

I'm not a powerhouse expert, but it sounds like your first idea is what I
first thought of, but stated in a different way.  Basically, my thought was
that those dataset(s) that needed to be shared would indeed be "in" their own
database, accessible by all, and those dataset(s) that are localized per
customer/company would be kept seperate.  I guess it is the fact that you ARE
using powerhouse that is tripping things up, because somehow powerhouse
itself needs to know that there are multiple "databases" at work here, and I
take it multiple DB's in powerhouse is not for the faint of heart?

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *