RE: Link AS400 database wirh Access Database

["Gary Monnier" <gary.monnier@xxxxxxxxxxxxx>]

Sachin,

Well, there is another way you can solve your problem.  We sell a
product called AuthorityBroker.  With it you can restrict your developer
access to objects unless they really need it.

AuthorityBroker lets you switch profiles on the fly.  With this product
you can 1) revoke your programmer's authority to the file and 2) allow
them to switch to a profile that has rights to access the data when it
is justified.  Each profile switch is tracked so you can report on what
someone did while they were switched.  It will also notify any
interested parties that the switch has occurred.

I won't go into a sales pitch here (although I'd love to), but if you're
interested you can go to our website www.powertechgroup.com/ for more
information.  You can download the product from there or call us at
253-872-7788.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chaudhary, Sachin
(GE Equipment Services,Consultant)
Sent: Friday, January 21, 2005 9:21 AM
To: Midrange Systems Technical Discussion
Subject: RE: Link AS400 database wirh Access Database
Importance: High


Yes you are right. There is already set of logical files and the
processing/reports etc go perfectly fine in production env. I just
wanted to do this for the new programmers who keep analysing data by
opening files and running SQLs time and again. We do not have a separate
test box:)

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Gary Monnier
Sent: Friday, January 21, 2005 10:50 AM
To: Midrange Systems Technical Discussion
Subject: RE: Link AS400 database wirh Access Database



There are many ways to solve your dilemma. One is, unless you really
have your heart set on doing this through Access, is to use a logical
file keyed in the sequence you want your query in and run your query
over the logical view.  Using this logical view will reduce the amount
of time and CPU your query uses.  And yes, it will take some CPU to
build the logical view, but you can schedule it to be created/installed
during slow hours.

If your file is really enormous you may be better off writing a program
to spin through it, filter out records you don't want to report on,
write those that you do want to report on to a separate physical file
and run your query over your new file.  




-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


-- 
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.