Comments on: View Data http://itknowledgeexchange.techtarget.com/itanswers/view-data/ Wed, 19 Jun 2013 09:51:42 +0000 hourly 1 By: gac http://itknowledgeexchange.techtarget.com/itanswers/view-data/#comment-55661 gac Wed, 13 Aug 2008 17:25:39 +0000 #comment-55661 Creating a view or logical file is a technical viable solution. Nonetheless, splitting each company’s data into two different libraries is a better approach, from my perspective.

Besides the possibility to do it (views) there are other considerations you might like to have: security and convenience.

Having each company’s data on different libraries simplifies security because you manage security at the library level instead of having to implement it at object level (and maybe even programmatically).

If the time comes when a third company must be added, you just simply mount the libraries structure for the company without having to change the programs.

Gerardo Agüero.

]]> By: graybeard52 http://itknowledgeexchange.techtarget.com/itanswers/view-data/#comment-55638 graybeard52 Tue, 12 Aug 2008 16:24:42 +0000 #comment-55638 A view ends up being basically the same thing as a LF, except it has no keys and response is usually slower (since the system doesn’t keep it up-to-date like it does a LF).

Another option is to create 2 libraries (one for each company) , and put the LF’s in them (one for each company). That way the LF’s can have the same name as the PF. Not something I like to do, but it can make working with 3rd party pgms easier, and reduce OVRDBF issues.

Comp 1 LIBL COMPLIB1, MAINLIBR, etc
Comp 2 LIBL COMPLIB2, MAINLIBR, etc

The comp 1 user will get the LF in COMPLIB1, etc,

]]>