by Clark Kellog » Fri, 13 Oct 2000 04:00:00
I wrote a sort test program to use the REMOVE statement and more fully
understand how it works and if I could use it in of my routines.
to create a quick dynamic array for testing, it failed to compile.
Huh?
All the programs I inherited use equates such as AM=CHAR(254). I had always
just followed this convention.
Now I curious about what is going on.
TIA
Regards
--
Clark
by Help Des » Sat, 14 Oct 2000 04:00:00
Regards
Noel
> I wrote a sort test program to use the REMOVE statement and more fully
> understand how it works and if I could use it in of my routines.
> to create a quick dynamic array for testing, it failed to compile.
> Huh?
> All the programs I inherited use equates such as AM=CHAR(254). I had
always
> just followed this convention.
> Now I curious about what is going on.
> TIA
> Regards
> --
> Clark
by Anthony W. Youngma » Sat, 14 Oct 2000 04:00:00
Posted At: 13 October 2000 12:08
Posted To: pick
Hi,
being in
D3. You will need to stick with the equates for the time being.
Regards
Noel
> Running AP/Pro native Version 6.1.15.a34
> I wrote a sort test program to use the REMOVE statement and more fully
> understand how it works and if I could use it in of my routines.
> to create a quick dynamic array for testing, it failed to compile.
> Huh?
> All the programs I inherited use equates such as AM=CHAR(254). I had
always
> just followed this convention.
> Now I curious about what is going on.
> TIA
> Regards
> --
> Clark
by mikepre.. » Sat, 14 Oct 2000 04:00:00
Mike.
being in
> D3. You will need to stick with the equates for the time being.
> Regards
> Noel
> > Running AP/Pro native Version 6.1.15.a34
> > I wrote a sort test program to use the REMOVE statement and more
fully
> > understand how it works and if I could use it in of my routines.
> > to create a quick dynamic array for testing, it failed to compile.
> > Huh?
> > All the programs I inherited use equates such as AM=CHAR(254). I
had
> always
> > just followed this convention.
> > Now I curious about what is going on.
> > TIA
> > Regards
> > --
> > Clark
by Don Verhage » Sat, 14 Oct 2000 04:00:00
--
Donald Verhagen
Platform:
HP-UX Unix, v10.x,
Unidata v4.1.x
System Builder
in
>D3. You will need to stick with the equates for the time being.
>Regards
>Noel
>> Running AP/Pro native Version 6.1.15.a34
>> I wrote a sort test program to use the REMOVE statement and more fully
>> understand how it works and if I could use it in of my routines.
>> to create a quick dynamic array for testing, it failed to compile.
>> Huh?
>> All the programs I inherited use equates such as AM=CHAR(254). I had
>always
>> just followed this convention.
>> Now I curious about what is going on.
>> TIA
>> Regards
>> --
>> Clark
by Homer L. Haze » Sat, 14 Oct 2000 04:00:00
When I define AM with an equate, I always EQU AM TO CHAR(254). I seem to
remember that FM was a char(255). It might have been on a Microdata Sequel.
I checked my R83 book and my AP/PRO book, but could find no reference to FM.
I no longer have the Microdata documents, so I cannot check there.
Larry Hazel
message
> -----Original Message-----
> Posted At: 13 October 2000 12:08
> Posted To: pick
> Hi,
> being in
> D3. You will need to stick with the equates for the time being.
> Regards
> Noel
> > Running AP/Pro native Version 6.1.15.a34
> > I wrote a sort test program to use the REMOVE statement and more fully
> > understand how it works and if I could use it in of my routines.
> and
> > to create a quick dynamic array for testing, it failed to compile.
> > Huh?
> > All the programs I inherited use equates such as AM=CHAR(254). I had
> always
> > just followed this convention.
> > Now I curious about what is going on.
> > TIA
> > Regards
> > --
> > Clark
by Anthony W. Youngma » Sat, 14 Oct 2000 04:00:00
And because I was brung up proper, like, I never use equates anyway. I
Posted At: 13 October 2000 15:19
Posted To: pick
Anthony,
When I define AM with an equate, I always EQU AM TO CHAR(254). I seem
to
remember that FM was a char(255). It might have been on a Microdata
Sequel.
I checked my R83 book and my AP/PRO book, but could find no reference to
FM.
I no longer have the Microdata documents, so I cannot check there.
Larry Hazel
message
is
> -----Original Message-----
> Posted At: 13 October 2000 12:08
> Posted To: pick
> Hi,
> being in
> D3. You will need to stick with the equates for the time being.
> Regards
> Noel
> > Running AP/Pro native Version 6.1.15.a34
> > I wrote a sort test program to use the REMOVE statement and more
fully
> > understand how it works and if I could use it in of my routines.
> and
> > to create a quick dynamic array for testing, it failed to compile.
> > Huh?
> > All the programs I inherited use equates such as AM=CHAR(254). I
had
> always
> > just followed this convention.
> > Now I curious about what is going on.
> > TIA
> > Regards
> > --
> > Clark
by Homer L. Haze » Sat, 14 Oct 2000 04:00:00
I still support clients on AP/PRO, so I try to not use a programming
technique unless it works for all of my clients. I hate to have to remember
I learned the EQUATE way back before R83 on Adds Mentor. It worked there,
it still works with D3. Why fix it if it ain't broke.
You were "brung up proper" so you don't use equates. I hate to burst your
doing. You are using a system or compiler defined equate rather than one
you choose to define, but it's the same thing - except you cannot choose to
add more.
I also prefer using an EQUATE to an assignment like VM = CHAR(253). You
cannot inadvertently change the EQUATE in the program. It's write
protected.
Larry Hazel
message
> And because I was brung up proper, like, I never use equates anyway. I
> -----Original Message-----
> Posted At: 13 October 2000 15:19
> Posted To: pick
> Anthony,
> When I define AM with an equate, I always EQU AM TO CHAR(254). I seem
> to
> remember that FM was a char(255). It might have been on a Microdata
> Sequel.
> I checked my R83 book and my AP/PRO book, but could find no reference to
> FM.
> I no longer have the Microdata documents, so I cannot check there.
> Larry Hazel
> message
> is
> > -----Original Message-----
> > Posted At: 13 October 2000 12:08
> > Posted To: pick
> > Hi,
> > being in
> > D3. You will need to stick with the equates for the time being.
> > Regards
> > Noel
> > > Running AP/Pro native Version 6.1.15.a34
> > > I wrote a sort test program to use the REMOVE statement and more
> fully
> > > understand how it works and if I could use it in of my routines.
> > and
> > > to create a quick dynamic array for testing, it failed to compile.
> > > Huh?
> > > All the programs I inherited use equates such as AM=CHAR(254). I
> had
> > always
> > > just followed this convention.
> > > Now I curious about what is going on.
> > > TIA
> > > Regards
> > > --
> > > Clark
by Anthony W. Youngma » Sat, 14 Oct 2000 04:00:00
You write portable code - I've only ever had to deal with one variant of
Pick in most of my pickie life, so I don't even know what is or isn't
portable (I've always worked for end users - 3 of them using the same
product).
Horses for courses - and I'm forever amazed at the amount of stuff I use
as a matter of course in INFORMATION that isn't available in older
Picks. All those statements I use that only exist as functions, etc etc.
The only time I've tried to write code on a genuine Pick I got very
badly burnt - and it was an interview competence test of all places! The
guy said INFORMATION and whatever this was were very similar - true but
they were different enough to burn me. I gather the interviewer thought
I was incompetent after he saw what I'd done.
variables, not equates. But I've never actually been able to look under
the bonnet, so I don't know. Anyways, we could both be right :-)
Cheers,
Wol.
Posted At: 13 October 2000 16:40
Posted To: pick
Anthony,
addressing.
I still support clients on AP/PRO, so I try to not use a programming
technique unless it works for all of my clients. I hate to have to
remember
I learned the EQUATE way back before R83 on Adds Mentor. It worked
there,
it still works with D3. Why fix it if it ain't broke.
You were "brung up proper" so you don't use equates. I hate to burst
your
are
doing. You are using a system or compiler defined equate rather than
one
you choose to define, but it's the same thing - except you cannot choose
to
add more.
I also prefer using an EQUATE to an assignment like VM = CHAR(253). You
cannot inadvertently change the EQUATE in the program. It's write
protected.
Larry Hazel
message
which
> is 255. I always do a double-take when people talk about "attributes"
> because I've only every worked with INFORMATION (and now UV) which
> always calls them fields.
> And because I was brung up proper, like, I never use equates anyway. I
> -----Original Message-----
> Posted At: 13 October 2000 15:19
> Posted To: pick
> Anthony,
> When I define AM with an equate, I always EQU AM TO CHAR(254). I seem
> to
> remember that FM was a char(255). It might have been on a Microdata
> Sequel.
> I checked my R83 book and my AP/PRO book, but could find no reference
to
> FM.
> I no longer have the Microdata documents, so I cannot check there.
> Larry Hazel
in
> message
> is
> > -----Original Message-----
> > Posted At: 13 October 2000 12:08
> > Posted To: pick
> > Hi,
> > being in
> > D3. You will need to stick with the equates for the time being.
> > Regards
> > Noel
> > > Running AP/Pro native Version 6.1.15.a34
> > > I wrote a sort test program to use the REMOVE statement and more
> fully
> > > understand how it works and if I could use it in of my routines.
> > and
> > > to create a quick dynamic array for testing, it failed to compile.
> > > Huh?
> > > All the programs I inherited use equates such as AM=CHAR(254). I
> had
> > always
> > > just followed this convention.
> > > Now I curious about what is going on.
> > > TIA
> > > Regards
> > > --
> > > Clark
by Perry Taylo » Sat, 14 Oct 2000 04:00:00
--
Perry Taylor
Canyon Data Solutions, Inc.
> When I define AM with an equate, I always EQU AM TO CHAR(254). I seem to
> remember that FM was a char(255). It might have been on a Microdata
Sequel.
> I checked my R83 book and my AP/PRO book, but could find no reference to
FM.
> I no longer have the Microdata documents, so I cannot check there.
> Larry Hazel
> message
> > -----Original Message-----
> > Posted At: 13 October 2000 12:08
> > Posted To: pick
> > Hi,
> > being in
> > D3. You will need to stick with the equates for the time being.
> > Regards
> > Noel
> > > Running AP/Pro native Version 6.1.15.a34
> > > I wrote a sort test program to use the REMOVE statement and more fully
> > > understand how it works and if I could use it in of my routines.
> > and
> > > to create a quick dynamic array for testing, it failed to compile.
> > > Huh?
> > > All the programs I inherited use equates such as AM=CHAR(254). I had
> > always
> > > just followed this convention.
> > > Now I curious about what is going on.
> > > TIA
> > > Regards
> > > --
> > > Clark
by Homer L. Haze » Sat, 14 Oct 2000 04:00:00
I didn't take your comments as being negative or attacking. People don't
always need a smiley. Just most of the time. I probably would have
responded the same even to a smiley. I might have worded my answer
differently, but I wanted to make a point.
what's happening inside the compiler. It may be an internal equate or a
write protected variable. My guess is that it's part of the syntax of the
language, and that the compiler substitutes appropriately. Sometimes it
will be the CHAR value, when it's an immediate operand or it will use the
address of a protected variable when it is an indirect operand. I was going
to say that one of the guys from Pick could peek under the hood and tell us
officially, but that would only be getting half of the story. We'd have to
get the same information from INFORMATION (UV) to see how close together
they are.
Don't worry about getting burned. I'm sure we've all done it. When I was
very young and visiting my first head hunter, he kept talking about this
language COBALT (spelled the way he pronounced it). All during the
interview he used that word. At the end, he told me he thought I was never
going to get a job since I was too stupid to realize he had been using the
wrong word. He didn't like it at all when I told him I was just being
polite and didn't think it was appropriate to correct him since I was
talking to him about a job.
Needless to say, I didn't hit it off with this head hunter and I never went
back.
You do good posts. Keep up the good work.
Larry Hazel
message
> You write portable code - I've only ever had to deal with one variant of
> Pick in most of my pickie life, so I don't even know what is or isn't
> portable (I've always worked for end users - 3 of them using the same
> product).
> Horses for courses - and I'm forever amazed at the amount of stuff I use
> as a matter of course in INFORMATION that isn't available in older
> Picks. All those statements I use that only exist as functions, etc etc.
> The only time I've tried to write code on a genuine Pick I got very
> badly burnt - and it was an interview competence test of all places! The
> guy said INFORMATION and whatever this was were very similar - true but
> they were different enough to burn me. I gather the interviewer thought
> I was incompetent after he saw what I'd done.
> variables, not equates. But I've never actually been able to look under
> the bonnet, so I don't know. Anyways, we could both be right :-)
> Cheers,
> Wol.
> -----Original Message-----
> Posted At: 13 October 2000 16:40
> Posted To: pick
> Anthony,
> addressing.
> I still support clients on AP/PRO, so I try to not use a programming
> technique unless it works for all of my clients. I hate to have to
> remember
> I learned the EQUATE way back before R83 on Adds Mentor. It worked
> there,
> it still works with D3. Why fix it if it ain't broke.
> You were "brung up proper" so you don't use equates. I hate to burst
> your
> are
> doing. You are using a system or compiler defined equate rather than
> one
> you choose to define, but it's the same thing - except you cannot choose
> to
> add more.
> I also prefer using an EQUATE to an assignment like VM = CHAR(253). You
> cannot inadvertently change the EQUATE in the program. It's write
> protected.
> Larry Hazel
> message
> which
> > is 255. I always do a double-take when people talk about "attributes"
> > because I've only every worked with INFORMATION (and now UV) which
> > always calls them fields.
> > And because I was brung up proper, like, I never use equates anyway. I
> > -----Original Message-----
> > Posted At: 13 October 2000 15:19
> > Posted To: pick
> > Anthony,
> > When I define AM with an equate, I always EQU AM TO CHAR(254). I seem
> > to
> > remember that FM was a char(255). It might have been on a Microdata
> > Sequel.
> > I checked my R83 book and my AP/PRO book, but could find no reference
> to
> > FM.
> > I no longer have the Microdata documents, so I cannot check there.
> > Larry Hazel
> in
> > message
> > is
> > > -----Original Message-----
> > > Posted At: 13 October 2000 12:08
> > > Posted To: pick
> > > Hi,
> > > being in
> > > D3. You will need to stick with the equates for the time being.
> > > Regards
> > > Noel
> > > > Running AP/Pro native Version 6.1.15.a34
> > > > I wrote a sort test program to use the REMOVE statement and more
> > fully
> > > > understand how it works and if I could use it in of my routines.
> > > > I failed not only to get the statement to work, but when I used
> > > and
> > > > to create a quick dynamic array for testing, it failed to compile.
> > > > Huh?
> > > > All the programs I inherited use equates such as AM=CHAR(254). I
> > had
> > > always
> > > > just followed this convention.
> > > > Now I curious about what is going on.
> > > > TIA
> > > > Regards
> > > > --
> > > > Clark
by Homer L. Haze » Sat, 14 Oct 2000 04:00:00
Segment mark. Thank you. I couldn't remember that, I was thinking FM was a
file marker or a frame marker. It was segment mark that I was remembering.
Larry Hazel
> --
> Perry Taylor
> Canyon Data Solutions, Inc.
> > Anthony,
> > When I define AM with an equate, I always EQU AM TO CHAR(254). I seem
to
> > remember that FM was a char(255). It might have been on a Microdata
> Sequel.
> > I checked my R83 book and my AP/PRO book, but could find no reference to
> FM.
> > I no longer have the Microdata documents, so I cannot check there.
> > Larry Hazel
> > message
is
> > > -----Original Message-----
> > > Posted At: 13 October 2000 12:08
> > > Posted To: pick
> > > Hi,
> > > being in
> > > D3. You will need to stick with the equates for the time being.
> > > Regards
> > > Noel
> > > > Running AP/Pro native Version 6.1.15.a34
> > > > I wrote a sort test program to use the REMOVE statement and more
fully
> > > > understand how it works and if I could use it in of my routines.
> > > and
> > > > to create a quick dynamic array for testing, it failed to compile.
> > > > Huh?
> > > > All the programs I inherited use equates such as AM=CHAR(254). I
had
> > > always
> > > > just followed this convention.
> > > > Now I curious about what is going on.
> > > > TIA
> > > > Regards
> > > > --
> > > > Clark
by Matti Lamprhe » Sat, 14 Oct 2000 04:00:00
Matti
by imhote » Sat, 14 Oct 2000 04:00:00
> I didn't take your comments as being negative or attacking. People don't
> always need a smiley. Just most of the time. I probably would have
> responded the same even to a smiley. I might have worded my answer
> differently, but I wanted to make a point.
> what's happening inside the compiler. It may be an internal equate or a
> write protected variable. My guess is that it's part of the syntax of the
> language, and that the compiler substitutes appropriately. Sometimes it
> will be the CHAR value, when it's an immediate operand or it will use the
> address of a protected variable when it is an indirect operand. I was
going
> to say that one of the guys from Pick could peek under the hood and tell
us
> officially, but that would only be getting half of the story. We'd have
to
> get the same information from INFORMATION (UV) to see how close together
> they are.
> Don't worry about getting burned. I'm sure we've all done it. When I was
> very young and visiting my first head hunter, he kept talking about this
> language COBALT (spelled the way he pronounced it). All during the
> interview he used that word. At the end, he told me he thought I was
never
> going to get a job since I was too stupid to realize he had been using the
> wrong word. He didn't like it at all when I told him I was just being
> polite and didn't think it was appropriate to correct him since I was
> talking to him about a job.
> Needless to say, I didn't hit it off with this head hunter and I never
went
> back.
> You do good posts. Keep up the good work.
> Larry Hazel
> message
> > Sorry, I think I should have put a smiley in there :-)
> > You write portable code - I've only ever had to deal with one variant of
> > Pick in most of my pickie life, so I don't even know what is or isn't
> > portable (I've always worked for end users - 3 of them using the same
> > product).
> > Horses for courses - and I'm forever amazed at the amount of stuff I use
> > as a matter of course in INFORMATION that isn't available in older
> > Picks. All those statements I use that only exist as functions, etc etc.
> > The only time I've tried to write code on a genuine Pick I got very
> > badly burnt - and it was an interview competence test of all places! The
> > guy said INFORMATION and whatever this was were very similar - true but
> > they were different enough to burn me. I gather the interviewer thought
> > I was incompetent after he saw what I'd done.
> > variables, not equates. But I've never actually been able to look under
> > the bonnet, so I don't know. Anyways, we could both be right :-)
> > Cheers,
> > Wol.
> > -----Original Message-----
> > Posted At: 13 October 2000 16:40
> > Posted To: pick
> > Anthony,
> > addressing.
> > I still support clients on AP/PRO, so I try to not use a programming
> > technique unless it works for all of my clients. I hate to have to
> > remember
> > I learned the EQUATE way back before R83 on Adds Mentor. It worked
> > there,
> > it still works with D3. Why fix it if it ain't broke.
> > You were "brung up proper" so you don't use equates. I hate to burst
> > your
> > are
> > doing. You are using a system or compiler defined equate rather than
> > one
> > you choose to define, but it's the same thing - except you cannot choose
> > to
> > add more.
> > I also prefer using an EQUATE to an assignment like VM = CHAR(253). You
> > cannot inadvertently change the EQUATE in the program. It's write
> > protected.
> > Larry Hazel
> > message
> > which
> > > is 255. I always do a double-take when people talk about "attributes"
> > > because I've only every worked with INFORMATION (and now UV) which
> > > always calls them fields.
> > > And because I was brung up proper, like, I never use equates anyway. I
> > > -----Original Message-----
> > > Posted At: 13 October 2000 15:19
> > > Posted To: pick
> > > Anthony,
> > > When I define AM with an equate, I always EQU AM TO CHAR(254). I seem
> > > to
> > > remember that FM was a char(255). It might have been on a Microdata
> > > Sequel.
> > > I checked my R83 book and my AP/PRO book, but could find no reference
> > to
> > > FM.
> > > I no longer have the Microdata documents, so I cannot check there.
> > > Larry Hazel
> > in
> > > message
> > > is
> > > > -----Original Message-----
> > > > Posted At: 13 October 2000 12:08
> > > > Posted To: pick
> > > > Hi,
> > > > being in
> > > > D3. You will need to stick with the equates for the time being.
> > > > Regards
> > > > Noel
> > > > > Running AP/Pro native Version 6.1.15.a34
> > > > > I wrote a sort test program to use the REMOVE statement and more
> > > fully
> > > > > understand how it works and if I could use it in of my routines.
> > > > > I failed not only to get the statement to work, but when I used
> > > > and
> > > > > to create a quick dynamic array for testing, it failed to compile.
> > > > > Huh?
> > > > > All the programs I inherited use equates such as AM=CHAR(254). I
> > > had
> > > > always
> > > > > just followed this convention.
> > > > > Now I curious about what is going on.
> > > > > TIA
> > > > > Regards
> > > > > --
> > > > > Clark
1. I am getting this message when i am tring to export or import anything using
I am getting this message when i am tring to export or import anything using
the DTS Import & Export wizard. Has anyone else encountered this and know
what the fix is?
3. Am I dumb?
4. ...:::[HelP]:::... Comparison between ADO 2.5 & ADO 2.6
5. dumb question but I am asking anyway
6. How To write stored procedures
7. I am a dumb, can't find enterprise manager
10. error ORA-01855: AM/A.M. or PM/P.M. required
11. Busy Day = Slowdown from 12 AM - 5 AM
12. Is this Possible Using DTS?Could you say the details.I am new