|
We solved this problem by doing the following: 1) We created an inquiry profile named MAPICSxy (xy is the environment designator) This profile has no special authority and cannot sign on. 2) Granted the MAPICSxy profile READ authority to a set of files within the specified environment 3) Added the MAPICSxy profile to the GRPPRF or SUPGRPPRF of the user needing access to the environment If a user needs access to more than one environment you simply add the MAPICSxy profile to their user profiles supplemental group. Another option would be to use authorization lists. You mention only ODBC. Does your application use the OBDC driver loaded on the PC or are you attaching to an ODBC driver running on a server. If you are using the server approach, what ID is the server driver using to attach to the AS/400? hrishikesh wrote: > We have started developing many PC programs that access Mapics Files via > ODBC & SQL. The users who use these PC programs are also Mapics Users. > Therefore, they already have atleast 'Read' access to Popular Mapics > files. But when the same users are trying to access the files from PC > programs, they get the following error message: <SNIP> Ron Hankey - CPIM Applications Programmer
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.