HP3000-L Archives

January 2001, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Steve Patterson <[log in to unmask]>
Reply To:
Steve Patterson <[log in to unmask]>
Date:
Mon, 22 Jan 2001 09:00:03 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (26 lines)
Thanks for all the replies, it would seem I may have been somewhat vague in
stating the need for releasing an individual dataset.

We have our fiinancials running using a third party product, with the entire
db housing the transactions, account definitions, etc., and as a result we
cannot modify the structure of the database in any way.  We have two main
production accounts, and in some cases our Powerhouse apps in one account
need to reference the chart of accounts dataset residing in the other
account, for data-entry validation.  To do this, we RELEASE the entire
financial db, but the auditors are concerned that we are making the whole db
accessible from any account.

Logic does *not* prevail when dealing with auditors.

It seems that the short answer is "no, you cannot release an individual
dataset", short of purchasing a product like MPEX (which isn't in the cards
right now).  I suppose we can make a flat file copy of the dataset(s) in
question, but I was hoping there was some other undocumented feature or
trick that we could use.

Thanks again for all the info.

Steve Patterson
Halifax Port Authority
www.portofhalifax.ca

ATOM RSS1 RSS2