This is theoretical. Right or wrong, we have business processes that are being run from Access databases. I have a business analyst who is trying to figure out how to update one field in an ISeries file after printing labels. He needs it in real time (or close to real time), it has to be within the confines of our security (SOX-based) -meaning that the users can't have update access to the file via the Access Database. Let's see, what else? We're discussing field level security, but the security administrator looked like a deer in the headlights when we mentioned it. We've also discussed having a stored procedure on the iSeries (which would have to submit a job under a different ID , I guess) or a function or using a trigger or "never ending" job.
So, how would you do this? How would you update fields from Access and still keep your files secure? Does anyone have any thoughts (besides "don't let the users use Access" - that ship sailed a long time ago).
Thanks! Have a good one.
So, how would you do this? How would you update fields from Access and still keep your files secure? Does anyone have any thoughts (besides "don't let the users use Access" - that ship sailed a long time ago).
Thanks! Have a good one.
Comment