Thank you all for your response:
I follow Colin's advice below and it worked ok now:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Marsh,
I read your response but it is a “little light†on detail, to say the
least. Based on what I understand of your note and attachment, here are my
comments as follows.
OK, so it seems that user authority to the file object is not an issue
contributing to your problem.
Seems you have two different LF’s - F56SSRLA and a newer one F56SSRLB. I
have to assume that obviously the existing one in production (F56SSRLA)
probably needs to stay because I presume it is being used for something
(you need to find out what it is used by and for what reason)
Now you have to:-
a) resolve which logical is the correct one for the program to use (look at
the program source code etc)
b) make sure that the program definitely uses the correct logical
c) test everything yourself in a test environment and make sure it works
d) set up a user with an appropriate LIBL to test the process in the test
environment.
If everything tests OK both for you and the user, then you need to plan out
what you have to do to migrate the change to the production environment. I
suggest that some steps might be:
Copy the modified source into the production source files
Compile the program(s) and new or modified logical (maybe F56SSRLB ??) in
production using the new source code in the production source library
Make any changes necessary to menus and/or DWV’s.
Make sure that F56SSRLB is not duplicated in any other libraries used for
normal user production processing
Sit with the user and monitor what happens when the user first uses the
“new†process
Cheers!
___________________
Marsh R Narewec
STC Computer Services
esolch
<esolch@mike-sell
s.com> To
Sent by:
[email protected]
jdeworld-bounces@ cc
jdelist.com
Subject
Re: CHAIN working for me BUT NOT
13/06/06 02:41 working for a User
Please respond to
JD Edwards® World
<jdeworld@jdelist
.com>
I've had this happen. You can check your code by using SETLL and READE to
see if the key really does exist as you think it does. I also think that
you have a lib list issue - the user isn't reading the same files you are
when the program is running.
Ellen Solch Systems Analyst/Administrator Mike-Sell's Potato Chips, Inc.