Re: MultiValue Visual Basic
- From: "Dave Mitchell" <mitch500@xxxxxxxxxxxx>
- Date: Thu, 27 Oct 2005 00:20:23 -0400
All I've done in that respect (in PICK) was to go down maybe two more
levels, but it was written right into a program, not done with a subroutine
or external program. It went something like this: (forgive any errors -
I'm doing this from memory....)
LOCATE "CCCC" IN STRING<3,4> SETTING POS
NEWSTRING = STRING<4,4,POS> ; ** SV of Attr 4, Value 4, may contain
chr(251) delimiters
CONVERT CHAR(251) TO CHAR(253) IN NEWSTRING
LOCATE "DDDD" IN NEWSTRING<1> SETTING NEWPOS
NEWSTRING<1,NEWPOS> = "EEEE"
CONVERT CHAR(253) TO CHAR(251) IN NEWSTRING
STRING = REPLACE(STRING,4,4,POS,NEWSTRING)
As far as i know, you can't have Optional arguments in a subroutine call in
PICK like you can in VB, so if you want a subroutine that will "dig down" as
far as char(128) as delimiters, you would need to call a subroutine with at
least 128 arguments. But if that's not a problem, it shouldn't be too hard
to write a simple recursive subroutine to do something like the above.
Dave
<michael@xxxxxxxxxx> wrote in message
news:1130385470.776673.22670@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Understood. What I'd like is to be able to write a delimited string out
> (from MV or VB) to a flat text file and then pcperform a command (with
> options) to perform the equivalent of the Pick string-handling
> functions on it capturing the results. More specifically, I'd like to
> break out of the constrictions inherent in the Pick/MV model - down
> below subvalue level. If you can provide the functionality I describe
> then it should be no harder really to go down from char(254) thru
> 253... all the way to char(128). Virtually unlimited nesting. This
> would be something I could use (pcperform) from within a PickBasic
> program or from VB.
>
> Mike.
>
.
- References:
- MultiValue Visual Basic
- From: Dave Mitchell
- Re: MultiValue Visual Basic
- From: Dave Mitchell
- Re: MultiValue Visual Basic
- From: michael
- MultiValue Visual Basic
- Prev by Date: Re: MultiValue Visual Basic
- Next by Date: Re: MultiValue Visual Basic
- Previous by thread: Re: MultiValue Visual Basic
- Next by thread: Re: MultiValue Visual Basic
- Index(es):