RE: [U2] Cannot access list ML_3516_1 Unidata phantom (MERGE.LIST)

2004-11-03 Thread Doyen Klein
Update: The program only failed when it included an open along with the MERGE.LIST command. The work-around, is to create a separate process which is phantom'd by the first phantom, this second process does the SAVE.LIST which the first process can read. No one has ever explained where the

RE: [U2] Cannot access list ML_3516_1 Unidata phantom (MERGE.LIST)

2004-11-01 Thread Alfke, Colin
You can use @LOGNAME to get the NT user that the phantom is logged in as. Do you really need to open the same file as the select? You can use fileinfo after you open it to show your permissions on it. What if you tried setting up a different VOC entry for that file? Maybe (but I doubt it) you

RE: [U2] Cannot access list ML_3516_1 Unidata phantom (MERGE.LIST)

2004-11-01 Thread Doyen Klein
Of Alfke, Colin Sent: Monday, November 01, 2004 9:21 AM To: [EMAIL PROTECTED] Subject: RE: [U2] Cannot access list ML_3516_1 Unidata phantom (MERGE.LIST) You can use @LOGNAME to get the NT user that the phantom is logged in as. Do you really need to open the same file as the select? You can

RE: [U2] Cannot access list ML_3516_1 Unidata phantom (MERGE.LIST)

2004-11-01 Thread Doyen Klein
] [mailto:owner-u2- [EMAIL PROTECTED] On Behalf Of Wally Terhune Sent: Monday, November 01, 2004 10:29 AM To: [EMAIL PROTECTED] Subject: Re: [U2] Cannot access list ML_3516_1 Unidata phantom (MERGE.LIST) UniData version and specific Windows platform? There was a Windows-specific problem

RE: [U2] Cannot access list ML_3516_1 Unidata phantom (MERGE.LIST)

2004-10-29 Thread Doyen Klein
Well suggested Charles and Colin . I had tried all lowercase knowing of the Pick flavor issue, but went with Colin's gET.LIST just for fun, Doesn't' work on the paragraph name (pARTLISTS is 'not found' but gET.LIST works just a well (or as poorly) as GET.LIST did. Charles, excellent idea,

RE: [U2] Cannot access list ML_3516_1 Unidata phantom (MERGE.LIST)

2004-10-29 Thread Alfke, Colin
Perhaps it's the user you're running the phantom as. Maybe there is a permission issue in the list directory. Hth Colin -Original Message- From: Doyen Klein [mailto:[EMAIL PROTECTED] Well suggested Charles and Colin . I had tried all lowercase knowing of the Pick flavor issue, but

RE: [U2] Cannot access list ML_3516_1 Unidata phantom (MERGE.LIST)

2004-10-29 Thread Doyen Klein
To: [EMAIL PROTECTED] Subject: RE: [U2] Cannot access list ML_3516_1 Unidata phantom (MERGE.LIST) Perhaps it's the user you're running the phantom as. Maybe there is a permission issue in the list directory. Hth Colin -Original Message- From: Doyen Klein [mailto:[EMAIL PROTECTED

RE: [U2] Cannot access list ML_3516_1 Unidata phantom (MERGE.LIST)

2004-10-28 Thread Doyen Klein
Bodine Sent: Wednesday, October 27, 2004 3:26 PM To: [EMAIL PROTECTED] Subject: RE: [U2] Cannot access list ML_3516_1 Unidata phantom (MERGE.LIST) Why dont you do a basic program with the UDTEXECUTE capturing all output and display the output to the screen. Then read the record

RE: [U2] Cannot access list ML_3516_1 Unidata phantom (MERGE.LIST)

2004-10-28 Thread Kathleené M Bodine
: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doyen Klein Sent: Thursday, October 28, 2004 4:58 AM To: [EMAIL PROTECTED] Subject: RE: [U2] Cannot access list ML_3516_1 Unidata phantom (MERGE.LIST) I did, in fact, originally each select was an individual UDTEXECUTE line. It makes

Re: [U2] Cannot access list ML_3516_1 Unidata phantom (MERGE.LIST)

2004-10-28 Thread Results
Doyen, Stupid thought... have you tried doing a DELETE.LIST before the SELECT and a CLEARSELECT after you are all done? If the SAVE.LIST is failing on permissions, the DELETE.LIST will solve it. If the second run is failing due to a hanging select or select pointer, the CLEARSELECT should

RE: [U2] Cannot access list ML_3516_1 Unidata phantom (MERGE.LIST)

2004-10-27 Thread Kathleené M Bodine
Why dont you do a basic program with the UDTEXECUTE capturing all output and display the output to the screen. Then read the record in the phantom (_PH_) file and see what the problem is. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doyen Klein Sent: