[UD] OPENSEQ, WEOFSEQ, CLOSESEQ

2004-04-13 Thread Shawn Waldie
Except for one possible inconsistency with the instructions regarding OPENSEQ, the documentation seems very straight-forward. However, I'm still missing something. My intention is to: 1) create a record (if it doesn't already exist) in a DIR-type file; 2) clear said record if data

RE: [UD] OPENSEQ, WEOFSEQ, CLOSESEQ

2004-04-13 Thread Shawn Waldie
That WAS the reason. Thank you very much. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 13, 2004 11:51 AM To: U2 Users Discussion List Subject: Re: [UD] OPENSEQ, WEOFSEQ, CLOSESEQ I may be over simplifying this but there appears to be a "STO

RE: [UD] OPENSEQ, WEOFSEQ, CLOSESEQ

2004-04-13 Thread Shawn Waldie
My main problem is resolved but your suggestions raised some other questions, Larry. When I take the initial WEOFSEQ out, the first run will produce the result I need. But if I run the program again, the error statement is returned each time the WRITESEQ statement is executed. When WEOFSEQ is exe

RE: [UD] OPENSEQ, WEOFSEQ, CLOSESEQ

2004-04-14 Thread Shawn Waldie
I'm back. I lost my machine yesterday afternoon. -Original Message- From: Larry Hiscock [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 13, 2004 2:21 PM To: 'U2 Users Discussion List' Subject: RE: [UD] OPENSEQ, WEOFSEQ, CLOSESEQ Comments inline: >What version of UD are you running? O

RE: [UD] OPENSEQ, WEOFSEQ, CLOSESEQ

2004-04-14 Thread Shawn Waldie
of the directory. hth -- Colin Alfke Calgary, Alberta Canada "Just because something isn't broken doesn't mean that you can't fix it" Stu Pickles >-Original Message- >From: Shawn Waldie [mailto:[EMAIL PROTECTED] >Sent: Tuesday, April 13, 2004 2:02 PM >To:

WEOFSEQ

2004-04-14 Thread Shawn Waldie
I need some clarification. Given the following: X.DIR = "X.HOME.WALDIES"; * the VOC item 'X.HOME.WALDIES' is a pointer to /home/waldies X.FILE = "SRW_TEST_SEQ.txt" OPENSEQ X.DIR,X.FILE TO FV.SEQ THEN WEOFSEQ FV.SEQ ELSE ... END Upon a successful open of X.DIR at X.FILE, will the WEO

RE: WEOFSEQ

2004-04-14 Thread Shawn Waldie
Got it. Thanks again, everyone. -Original Message- From: Shawn Waldie Sent: Wednesday, April 14, 2004 11:49 AM To: U2 Users Discussion List Subject: WEOFSEQ I need some clarification... -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users

RE: [UD] LPTR

2004-01-27 Thread Shawn Waldie
LF's without CR's - unless the printer is configured to convert LF to CRLF or course. cheers Mats Shawn Waldie wrote: >I'm a little out of my element on this, but I'm sure someone here has >the answer. > >Right now, if I execute "LIST PERSON LAST.NAME

UniDebugger

2004-02-05 Thread Shawn Waldie
Is there a setting in UniDebugger that will allow me to edit and keep open a file (program or PA) without locking it - so I can test it in the DC pane without first closing the editor? I could do this with HyperEdit, so I'm assuming I can do it with dbugger. TIA Shawn -- u2-users mailing list [

RE: EVAL and LIKE

2004-02-05 Thread Shawn Waldie
Title: Message If all you need is just a count of records in a file with a particular field containing the value "*" or "Incomplete":   COUNT file WITH field = '*' 'Incomplete' -Original Message-From: Kevin Michaelsen [mailto:[EMAIL PROTECTED] Sent: Thursday, February 05, 2004

RE: UniDebugger

2004-02-05 Thread Shawn Waldie
That didn't make sense, did it. No wonder I wasn't getting any responses. I even had my cup 'o coffee. I'm leaving now... -Original Message- From: Shawn Waldie Sent: Thursday, February 05, 2004 9:55 AM To: U2 Users Discussion List Subject: UniDebugger I

RE: UniDebugger

2004-02-05 Thread Shawn Waldie
re are no locks left on the UV server. I just have to save before doing any compiling. I did have to make sure the BASIC files were type 19, and not type 1. -----Original Message- From: Shawn Waldie [mailto:[EMAIL PROTECTED] Sent: Thursday, February 05, 2004 11:55 AM To: U2 Users Discussion List S