Having not followed the complete thread I have these thoughts: This sounds like situation for Authorization lists. What you would do is establish group profiles for each company. Setup up Authorization lists for the applications that you would want the company to access containing the group profile. Assign the users to the appropriate group. Now understand that if the data is in the same file, you would want to establish logicals or coding (company code, etc) to limit cross data access. Multi member files are another way to do this, your CLPs can retrieve the user profile information and decide from the user profile information which OVRDBF to use. This can get messy depending on how many exceptions and customization you will need to make. Remember that any customization needs to be documented and a change management process developed and maintained. Due to the nature of Authorization lists you would need to create a program that produces a listing of all authorization lists with their contents. Hope this helps. Julio Domingo Systems Analyst American General Finance
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.