Mobile: (303) 807-6222
> wterh...@rocketsoftware.com
> u2supp...@rocketsoftware.com
>
> From: u2-users-boun...@listserver.u2ug.org
> [u2-users-boun...@listserver.u2ug.org] On Behalf Of Karl Pearson
> [ka...@ourldsfamily.com]
> Sent: Friday, Jan
(303) 807-6222
>> wterh...@rocketsoftware.com
>> u2supp...@rocketsoftware.com
>>
>> From: u2-users-boun...@listserver.u2ug.org
>> [u2-users-boun...@listserver.u2ug.org] On Behalf Of Karl Pearson
>> [ka...@ourldsfamily.com]
>> Sent:
ftware.com
From: u2-users-boun...@listserver.u2ug.org
[u2-users-boun...@listserver.u2ug.org] On Behalf Of Karl Pearson
[ka...@ourldsfamily.com]
Sent: Friday, January 08, 2010 12:12 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] ITYPE BASIC use?
I have a client who would like to use the uniV
To: u2-users@listserver.u2ug.org
> Subject: [U2] ITYPE BASIC use?
>
> I have a client who would like to use the uniVerse ITYPE function but
> the HELP (HELP BASIC ITYPE) documentation is wrong.
>
> For example, here's a sample piece of code, which duplicates the HELP
> code
-users-boun...@listserver.u2ug.org] On Behalf Of Karl Pearson
[ka...@ourldsfamily.com]
Sent: Friday, January 08, 2010 12:12 PM
To: u2-users@listserver.u2ug.org
Subject: [U2] ITYPE BASIC use?
I have a client who would like to use the uniVerse ITYPE function but
the HELP (HELP BASIC ITYPE
You are, of course, correct. If your itype does not reference the id field of
the record, then I do not necessary to assign @id.
My bias towards always assigning it comes from experience writing utilities,
where no such assumptions may be made, rather then writing code dependent on
the individ
In message , Rick
Nuckolls writes
I doubt that I will be the only one to reply, but
The variables "@id" and "@record" must be set prior to the call, as in:
Note that both of these are *optional* *if* they aren't used.
But it's extremely unlikely you won't use at least one of them. I don'
The documentation states to assign a value to variable @RECORD first
otherwise the code will fail.
So instead of "read REC from CONF,KEY then" try "read @RECORD from
CONF,KEY then"
Karl Pearson wrote:
> I have a client who would like to use the uniVerse ITYPE function but
> the HELP (HELP BASIC IT
Oops,
left one "KEY" in the code.
-Rick
> I doubt that I will be the only one to reply, but
>
> The variables "@id" and "@record" must be set prior to the call, as in:
>
>> 14 loop
> readnext @id else
> exit
> end
>> 16
>
I doubt that I will be the only one to reply, but
The variables "@id" and "@record" must be set prior to the call, as in:
> 14 loop
readnext @id else
exit
end
> 16
read @record from CONF,KEY then
> 18
I have a client who would like to use the uniVerse ITYPE function but
the HELP (HELP BASIC ITYPE) documentation is wrong.
For example, here's a sample piece of code, which duplicates the HELP
code sample:
6 DONE = 0
7
8 open "DICT","CONF" to D.CONF else stopm "No DICT CONF file"
11 matches
Mail list logo