Don Verhagen wrote:
Jason,
Unless it's a typo, you quoted the "TEST_XML_HANDEL" variable in your
OpenXMLData statement
Should by STATUS = OpenXMLData(TEST_XML_HANDEL,.) not
OpenXMLData("TEST_XML_HANDEL",...)
Don V
Don,
I you read my original posting closely, you will see I have al
I'm a little confused where dictionaries come into play with compiled versus
interpreted programs. I've worked on interpretive basic system and
dictionaries don't have anything to do with it.
Unless it's a 3rd form of programming, ie parameter driven.
Thanks
Mark Johnson
- Original Message --
Jason,
Unless it's a typo, you quoted the "TEST_XML_HANDEL" variable in your
OpenXMLData statement
Should by STATUS = OpenXMLData(TEST_XML_HANDEL,.) not
OpenXMLData("TEST_XML_HANDEL",...)
Don V
>>> On 11/17/2006 at 7:11 pm, in message
<[EMAIL PROTECTED]>, [EMAIL PROTECTED]
wrote:
> Hi g
Then h I got it right
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Tom Dodds
Sent: Saturday, November 18, 2006 7:17 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [UV] Question about EQU
The way I understand this thing is that w
The way I understand this thing is that when you use a simple variable (A=
16) what is stored in the object code is an offset value into the descriptor
table where the value of A is stored. If you use an EQU A to 16 then what
is stored in the object code is 16. When the program is executed the
in
Wouldn't it then be that anything that is using compiled rather than
interpretive is faster...
i.e. Basic rather than dictionaries...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Kevin King
Sent: Saturday, November 18, 2006 1:06 AM
To: u2-users@listserv
I'll take a stab at this.
EQU, which is a compile time construct shouldn't make ANY difference. In
real time, it probably doesn't.
But, back in the old days on PICK implementations (I don't know if it's
still this way), the compiler inserted a "NO-OP" (no operation instruction)
into the obje
