RE: [U2] Re: Move data files from Unidata to Universe
If this is a one-off deal, they can both talk to DIR/type 1/19 files
And or if you have a copy of AccuTerm and are not talking too many
million records, FTPICK
If you just need to read/write some data, and don't want to introduce
.NET middleware, then maybe a simple socket server in Basic?
Ross Ferris
Stamina Software
Visage Better by Design!
-Original Message-
From: [EMAIL PROTECTED] [mailto:owner-u2-
[EMAIL PROTECTED] On Behalf Of Scott Ballinger
Sent: Wednesday, 25 July 2007 11:11 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] Re: Move data files from Unidata to Universe
UPDATE:
Here is a response I received from IBM:
Scott,
I have checked with our Lab Services (aka consulting) group and they
tell
me that there have been no requests to migrate a UniData account to
UniVerse, and there are no native utilities within UniVerse to do this.
They are willing to discuss this with you as a billable engagement.
FYI, if this had been the inverse .. migrating a UV account to UniData,
it
would have been no problem, as UniData comes bundled with a command
called
UV_RESTORE, which takes a uvbackup sourced account and restores and
converts it to UniData file formats.
So perhaps there is another way to skin this cat. Is there a way to
read/write to UDT files directly from UV?
Any and all off-the-wall, out-of-the-box, out-of-left-field, {insert
your
favorite left-brained-business-creativity-MBA cliche here} suggestions
welcome.
/Scott Ballinger
Pareto Corporation
Edmonds WA USA
206 713 6006
On 7/23/07, Scott Ballinger [EMAIL PROTECTED] wrote:
I have a Unidata demo on my pc that I installed along the the PE
version
of Unidata. I want to test in my Universe/Linux environment. How does
one
convert a Unidata account to Universe? (I am ok with the ud style
dicts, so
I just need to convert the data files, indexes? etc.) It has been
suggested
that uvbackup can do this.
/Scott Ballinger
Pareto Corporation
Edmonds WA USA
206 713 6006
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Re: Move data files from Unidata to Universe
A relatively easy and 'simple' way to read/write UD files from UV (or
vice versa) is to use BCI.
We use BCI to communicate and transfer data to/from remote UV database
servers. It works fine for our purposes. There is no reason why the
remove server can't be a UD database (provided it supports BCI, of
course).
We do it by calling a subroutine on the remote host, as a SQL stored
proceedure. We past what we want to do to (read/write) the routine and
the associated data is passed (dynamic array) to or from the client
application. It works well for us. We do simple record at a time type
transfers, emulating the PI-style COPY verb.
Regards
David
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Scott Ballinger
Sent: Wednesday, July 25, 2007 11:11 AM
To: u2-users@listserver.u2ug.org
Subject: [U2] Re: Move data files from Unidata to Universe
UPDATE:
Here is a response I received from IBM:
Scott,
I have checked with our Lab Services (aka consulting) group and they
tell me that there have been no requests to migrate a UniData account to
UniVerse, and there are no native utilities within UniVerse to do this.
They are willing to discuss this with you as a billable engagement.
FYI, if this had been the inverse .. migrating a UV account to UniData,
it would have been no problem, as UniData comes bundled with a command
called UV_RESTORE, which takes a uvbackup sourced account and restores
and converts it to UniData file formats.
So perhaps there is another way to skin this cat. Is there a way to
read/write to UDT files directly from UV?
Any and all off-the-wall, out-of-the-box, out-of-left-field, {insert
your favorite left-brained-business-creativity-MBA cliche here}
suggestions welcome.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Re: Move data files from Unidata to Universe
From: doug chanco [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Tuesday, July 24, 2007 11:25 PM Subject: Re: [U2] Re: Move data files from Unidata to Universe I can confirm (that ud/uv will run fine on the same system) as I currently run jBASE 4.1, unidata 7.x amd universe 10.x on the same virtual machine running linux (centos to be exact (free version fo red hats advanced sever 4.0)) and they all work just fine together dougc Yet another glaring example of: Just because you CAN, doesn't mean you SHOULD Especially where any type of production environment may come into play. Regards, Scott Richardson Senior Systems Engineer / Consultant Product Support Engineer Marlborough, MA 01752 DPMonitor - http://www.deltek.us --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
[U2] [u2] : Cleaner Case Statement
How can this structure be cleaned-up? begin case case Ans = 'A' ; gosub Check.A case Ans = 'B' ; gosub Check.B case Ans = '2' ; gosub Check.B end case The following is more difficult to read. begin case case Ans = 'A' ; gosub Check.A case Ans = 'B' or Ans = '2' ; gosub Check.B end case I would like something like... begin case case Ans = 'A' ; gosub Check.A case Ans = 'B' case Ans = '2' ; gosub Check.B end case so that the gosub Check.B command is not repeated. I have tried a few alternatives without a victory. Suggestions would be appreciated. --Bill --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [u2] : Cleaner Case Statement
The 2nd set of syntax is the only one that will work if you want to do the GOSUB when ANS equals either B or 2. I don't agree that it's hard to read, but I don't like having multiple statements on one line, separated by semicolons, I prefer to have the case and the gosub on separate lines, but that's a matter of personal preference. Karen -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brutzman, Bill Sent: Wednesday, July 25, 2007 11:49 AM To: 'u2-users@listserver.u2ug.org' Subject: [U2] [u2] : Cleaner Case Statement How can this structure be cleaned-up? begin case case Ans = 'A' ; gosub Check.A case Ans = 'B' ; gosub Check.B case Ans = '2' ; gosub Check.B end case The following is more difficult to read. begin case case Ans = 'A' ; gosub Check.A case Ans = 'B' or Ans = '2' ; gosub Check.B end case I would like something like... begin case case Ans = 'A' ; gosub Check.A case Ans = 'B' case Ans = '2' ; gosub Check.B end case so that the gosub Check.B command is not repeated. I have tried a few alternatives without a victory. Suggestions would be appreciated. --Bill --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [u2] : Cleaner Case Statement
On 7/25/07, Brutzman, Bill [EMAIL PROTECTED] wrote: How can this structure be cleaned-up? begin case case Ans = 'A' ; gosub Check.A case Ans = 'B' ; gosub Check.B case Ans = '2' ; gosub Check.B end case If this is all you need, why not: IF (Ans = 'A') THEN GOSUB Check.A END ELSE GOSUB Check.B END Or is your example a simplification? -Kevin http://www.PrecisOnline.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [u2] : Cleaner Case Statement
Try this
ON index('AB2',Ans,1) GOSUB Check.A, Check.B, Check.B
Manu
- Original Message -
From: Brutzman, Bill [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, July 25, 2007 5:48 PM
Subject: [U2] [u2] : Cleaner Case Statement
How can this structure be cleaned-up?
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' ; gosub Check.B
case Ans = '2' ; gosub Check.B
end case
The following is more difficult to read.
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' or Ans = '2' ; gosub Check.B
end case
I would like something like...
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B'
case Ans = '2' ; gosub Check.B
end case
so that the gosub Check.B command is not repeated. I have tried a few
alternatives without a victory.
Suggestions would be appreciated.
--Bill
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [u2] : Cleaner Case Statement
Hi Bill, Unlike languages such as C, Basic does not allow multiple conditions in the way in which you are looking to do. In terms of run time performance or program size, if it really is just a GOSUB, there whould be little disadvantage in writing the more verbose form of your first example. Martin Phillips Ladybridge Systems Ltd 17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB +44-(0)1604-709200 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [u2] : Cleaner Case Statement
case Ans = 'B' in the third set means do nothing when Ans = 'B', and stop evaluating cases. Surely you wouldn't wish to break millions of lines of code by changing the meaning of the case syntax. The gosubs should go on their own line. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brutzman, Bill Sent: Wednesday, July 25, 2007 11:49 AM To: 'u2-users@listserver.u2ug.org' Subject: [U2] [u2] : Cleaner Case Statement How can this structure be cleaned-up? begin case case Ans = 'A' ; gosub Check.A case Ans = 'B' ; gosub Check.B case Ans = '2' ; gosub Check.B end case The following is more difficult to read. begin case case Ans = 'A' ; gosub Check.A case Ans = 'B' or Ans = '2' ; gosub Check.B end case I would like something like... begin case case Ans = 'A' ; gosub Check.A case Ans = 'B' case Ans = '2' ; gosub Check.B end case so that the gosub Check.B command is not repeated. I have tried a few alternatives without a victory. Suggestions would be appreciated. --Bill --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [u2] : Cleaner Case Statement
The first structure emphasizes program flow based on Ans and is very readable. The second structure show program branching and is also readable. Another approach might be thus: Alpha.Cmds= Alpha.Cmds1, -1 = A Beta.Cmds = Beta.Cmds1, -1 = B Beta.Cmds1, -1 = 2 ... begin case case Ans matches Alpha.Cmds ; gosub Check.A case Ans matches Beta.Cmds ; gosub Check.B end case David A. Green DAG Consulting 480.813.1725 -Original Message- How can this structure be cleaned-up? begin case case Ans = 'A' ; gosub Check.A case Ans = 'B' ; gosub Check.B case Ans = '2' ; gosub Check.B end case The following is more difficult to read. begin case case Ans = 'A' ; gosub Check.A case Ans = 'B' or Ans = '2' ; gosub Check.B end case I would like something like... begin case case Ans = 'A' ; gosub Check.A case Ans = 'B' case Ans = '2' ; gosub Check.B end case so that the gosub Check.B command is not repeated. I have tried a few alternatives without a victory. Suggestions would be appreciated. --Bill --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [u2] : Cleaner Case Statement
Kevin, What if the answer is Q? I almost always put in a CASE 1 statement to catch anything that resulted from a later code revision by a colleague or someone who follows me in a job! (The 'almost' is to exclude one-shot programs that nobody should ever run again.) Susan Lynch F.W. Davison Company, Inc. - Original Message - From: Kevin King [EMAIL PROTECTED] To: u2-users@listserver.u2ug.org Sent: Wednesday, July 25, 2007 12:16 PM Subject: Re: [U2] [u2] : Cleaner Case Statement On 7/25/07, Brutzman, Bill [EMAIL PROTECTED] wrote: How can this structure be cleaned-up? begin case case Ans = 'A' ; gosub Check.A case Ans = 'B' ; gosub Check.B case Ans = '2' ; gosub Check.B end case If this is all you need, why not: IF (Ans = 'A') THEN GOSUB Check.A END ELSE GOSUB Check.B END Or is your example a simplification? -Kevin http://www.PrecisOnline.com --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [u2] : Cleaner Case Statement
Not good if answer is not limited to one character wide.
Isn't ON GOSUB out of style?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Manu Fernandes
Sent: Wednesday, July 25, 2007 12:44 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [u2] : Cleaner Case Statement
Try this
ON index('AB2',Ans,1) GOSUB Check.A, Check.B, Check.B
Manu
- Original Message -
From: Brutzman, Bill [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, July 25, 2007 5:48 PM
Subject: [U2] [u2] : Cleaner Case Statement
How can this structure be cleaned-up?
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' ; gosub Check.B
case Ans = '2' ; gosub Check.B
end case
The following is more difficult to read.
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' or Ans = '2' ; gosub Check.B
end case
I would like something like...
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B'
case Ans = '2' ; gosub Check.B
end case
so that the gosub Check.B command is not repeated. I have tried a
few alternatives without a victory.
Suggestions would be appreciated.
--Bill
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [u2] : Cleaner Case Statement
Someone want to explain to me why ON GOSUB is bdd ?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Karen Bessel
Sent: Wednesday, July 25, 2007 1:06 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [u2] : Cleaner Case Statement
ON GOSUB..Bad. Bill, that is a bad coding practice -
don't go there.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Manu Fernandes
Sent: Wednesday, July 25, 2007 12:44 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [u2] : Cleaner Case Statement
Try this
ON index('AB2',Ans,1) GOSUB Check.A, Check.B, Check.B
Manu
- Original Message -
From: Brutzman, Bill [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, July 25, 2007 5:48 PM
Subject: [U2] [u2] : Cleaner Case Statement
How can this structure be cleaned-up?
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' ; gosub Check.B
case Ans = '2' ; gosub Check.B
end case
The following is more difficult to read.
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' or Ans = '2' ; gosub Check.B
end case
I would like something like...
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B'
case Ans = '2' ; gosub Check.B
end case
so that the gosub Check.B command is not repeated. I have tried a
few
alternatives without a victory.
Suggestions would be appreciated.
--Bill
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for
the sole use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. ZirMed, Inc. has strict policies regarding the
content of e-mail communications, specifically Protected Health Information,
any communications containing such material will be returned to the originating
party with such advisement noted. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [u2] : Cleaner Case Statement
Just to be different...
Why not add a new label called Check.2 put it right before the label
Check.B
Then the code would look like:
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' ; gosub Check.B
case Ans = '2' ; gosub Check.2
case 1 ; gosub error.condition or null
end case
This would help from a maintenance standpoint, if later on Check.2
needed it's own code differing than Check.B
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave Davis
Sent: Wednesday, July 25, 2007 1:22 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [u2] : Cleaner Case Statement
Not good if answer is not limited to one character wide.
Isn't ON GOSUB out of style?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Manu Fernandes
Sent: Wednesday, July 25, 2007 12:44 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [u2] : Cleaner Case Statement
Try this
ON index('AB2',Ans,1) GOSUB Check.A, Check.B, Check.B
Manu
- Original Message -
From: Brutzman, Bill [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, July 25, 2007 5:48 PM
Subject: [U2] [u2] : Cleaner Case Statement
How can this structure be cleaned-up?
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' ; gosub Check.B
case Ans = '2' ; gosub Check.B
end case
The following is more difficult to read.
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' or Ans = '2' ; gosub Check.B
end case
I would like something like...
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B'
case Ans = '2' ; gosub Check.B
end case
so that the gosub Check.B command is not repeated. I have tried a
few alternatives without a victory.
Suggestions would be appreciated.
--Bill
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [u2] : Cleaner Case Statement
I don't know either - this thread is the 1st time I ever heard that one.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Perry Taylor
Sent: July 25, 2007 02:53 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [u2] : Cleaner Case Statement
Someone want to explain to me why ON GOSUB is bdd ?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Karen Bessel
Sent: Wednesday, July 25, 2007 1:06 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [u2] : Cleaner Case Statement
ON GOSUB..Bad. Bill, that is a bad coding practice -
don't go there.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Manu Fernandes
Sent: Wednesday, July 25, 2007 12:44 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [u2] : Cleaner Case Statement
Try this
ON index('AB2',Ans,1) GOSUB Check.A, Check.B, Check.B
Manu
- Original Message -
From: Brutzman, Bill [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, July 25, 2007 5:48 PM
Subject: [U2] [u2] : Cleaner Case Statement
How can this structure be cleaned-up?
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' ; gosub Check.B
case Ans = '2' ; gosub Check.B
end case
The following is more difficult to read.
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' or Ans = '2' ; gosub Check.B
end case
I would like something like...
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B'
case Ans = '2' ; gosub Check.B
end case
so that the gosub Check.B command is not repeated. I have tried a
few
alternatives without a victory.
Suggestions would be appreciated.
--Bill
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. ZirMed, Inc. has strict
policies regarding the content of e-mail communications, specifically
Protected Health Information, any communications containing such
material will be returned to the originating party with such advisement
noted. If you are not the intended recipient, please contact the sender
by reply e-mail and destroy all copies of the original message.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [u2] : Cleaner Case Statement
You still have an oxhp.com address? I thought that oxhp was gone?
How're you doin'?
Dan Fitzgerald
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rotella, Leon M.
Sent: Wednesday, July 25, 2007 2:54 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [u2] : Cleaner Case Statement
Just to be different...
Why not add a new label called Check.2 put it right before the label
Check.B
Then the code would look like:
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' ; gosub Check.B
case Ans = '2' ; gosub Check.2
case 1 ; gosub error.condition or null
end case
This would help from a maintenance standpoint, if later on Check.2
needed it's own code differing than Check.B
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave Davis
Sent: Wednesday, July 25, 2007 1:22 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [u2] : Cleaner Case Statement
Not good if answer is not limited to one character wide.
Isn't ON GOSUB out of style?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Manu Fernandes
Sent: Wednesday, July 25, 2007 12:44 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [u2] : Cleaner Case Statement
Try this
ON index('AB2',Ans,1) GOSUB Check.A, Check.B, Check.B
Manu
- Original Message -
From: Brutzman, Bill [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, July 25, 2007 5:48 PM
Subject: [U2] [u2] : Cleaner Case Statement
How can this structure be cleaned-up?
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' ; gosub Check.B
case Ans = '2' ; gosub Check.B
end case
The following is more difficult to read.
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' or Ans = '2' ; gosub Check.B
end case
I would like something like...
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B'
case Ans = '2' ; gosub Check.B
end case
so that the gosub Check.B command is not repeated. I have tried a
few alternatives without a victory.
Suggestions would be appreciated.
--Bill
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Cleaner Case Statement
ON is bad because it is in violation of the KISS principle. (Keep It So
Simple)
--Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Perry Taylor
Sent: Wednesday, July 25, 2007 2:53 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [u2] : Cleaner Case Statement
Someone want to explain to me why ON GOSUB is bdd ?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Karen Bessel
Sent: Wednesday, July 25, 2007 1:06 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [u2] : Cleaner Case Statement
ON GOSUB..Bad. Bill, that is a bad coding practice -
don't go there.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Manu Fernandes
Sent: Wednesday, July 25, 2007 12:44 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [u2] : Cleaner Case Statement
Try this
ON index('AB2',Ans,1) GOSUB Check.A, Check.B, Check.B
Manu
- Original Message -
From: Brutzman, Bill [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, July 25, 2007 5:48 PM
Subject: [U2] [u2] : Cleaner Case Statement
How can this structure be cleaned-up?
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' ; gosub Check.B
case Ans = '2' ; gosub Check.B
end case
The following is more difficult to read.
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' or Ans = '2' ; gosub Check.B
end case
I would like something like...
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B'
case Ans = '2' ; gosub Check.B
end case
so that the gosub Check.B command is not repeated. I have tried a
few
alternatives without a victory.
Suggestions would be appreciated.
--Bill
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain confidential
and privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. ZirMed, Inc. has strict policies regarding the
content of e-mail communications, specifically Protected Health Information,
any communications containing such material will be returned to the
originating party with such advisement noted. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all copies
of the original message.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Cleaner Case Statement
Hold the phone... That's a valid syntax? On what platform? On 7/25/07, Martin Phillips [EMAIL PROTECTED] wrote: ON is bad because it is in violation of the KISS principle. (Keep It So Simple) You have to be kidding! Consider a simple menu option processor... INPUT OPTION IF OPTION MATCHES '1N' THEN ON OPTION GOSUB OPTION1, ;* helpful comment OPTION2, ;* blah bah OPTION3, ;* blah blah ERROR END --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Cleaner Case Statement
Readability = better maintainability ON/GOSUB # Readability ThereforeON/GOSUB # better maintainability. As one of my teenaged daughters would say, ON/GOSUB is sooo 1980s. :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin Phillips Sent: Wednesday, July 25, 2007 4:28 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] Cleaner Case Statement ON is bad because it is in violation of the KISS principle. (Keep It So Simple) You have to be kidding! Consider a simple menu option processor... INPUT OPTION IF OPTION MATCHES '1N' THEN ON OPTION GOSUB OPTION1, ;* helpful comment OPTION2, ;* blah bah OPTION3, ;* blah blah ERROR END compared with INPUT OPTION BEGIN CASE CASE OPTION = 1 GOSUB OPTION1 ;* helpful comment CASE OPTION = 2 GOSUB OPTION2 ;* blah blah CASE OPTION = 3 GOSUB OPTION3 ;* blah blah CASE 1 GOSUB ERROR END CASE Personally, I find the first one much neater and simpler. It gets more so as the list of options grows. It will also be faster to execute, not that this is likely to be much of a problem. Let's not turn this into yet another debate about coding style but just accept that we each have our own preferences. Martin Phillips Ladybridge Systems Ltd 17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB +44-(0)1604-709200 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] [u2] : Cleaner Case Statement
One possible reason why it might be considered less than optimal:
From the UniData Basic Commands manual:
...If expr is less than or equal to 1, UniData transfers program control to
the subroutine starting at the first label in the list...
So if ANS is Q in the code fragment below, you gosub Check.A. (Unless you
are using BASICTYPE P or BASICTYPE M, in which case it drops to the next
line of code - that is from a note on the previous page to the last
quote...) If that is what you really want, ok, but it is certainly not going
to be clear to the next poor soul who has to maintain the code! Or who
might change the BASICTYPE and not realize the impact that it would have on
your logic...
Susan Lynch
F. W. Davison Company, Inc.
- Original Message -
From: gerry-u2ug [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, July 25, 2007 3:36 PM
Subject: RE: [U2] [u2] : Cleaner Case Statement
I don't know either - this thread is the 1st time I ever heard that one.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Perry Taylor
Sent: July 25, 2007 02:53 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [u2] : Cleaner Case Statement
Someone want to explain to me why ON GOSUB is bdd ?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Karen Bessel
Sent: Wednesday, July 25, 2007 1:06 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [u2] : Cleaner Case Statement
ON GOSUB..Bad. Bill, that is a bad coding practice -
don't go there.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Manu Fernandes
Sent: Wednesday, July 25, 2007 12:44 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [u2] : Cleaner Case Statement
Try this
ON index('AB2',Ans,1) GOSUB Check.A, Check.B, Check.B
Manu
- Original Message -
From: Brutzman, Bill [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, July 25, 2007 5:48 PM
Subject: [U2] [u2] : Cleaner Case Statement
How can this structure be cleaned-up?
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' ; gosub Check.B
case Ans = '2' ; gosub Check.B
end case
The following is more difficult to read.
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' or Ans = '2' ; gosub Check.B
end case
I would like something like...
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B'
case Ans = '2' ; gosub Check.B
end case
so that the gosub Check.B command is not repeated. I have tried a
few
alternatives without a victory.
Suggestions would be appreciated.
--Bill
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution is prohibited. ZirMed, Inc. has strict
policies regarding the content of e-mail communications, specifically
Protected Health Information, any communications containing such
material will be returned to the originating party with such advisement
noted. If you are not the intended recipient, please contact the sender
by reply e-mail and destroy all copies of the original message.
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] : Cleaner Case Statement
To answer the question... that was not the original question.
The original question is just under I would like something like...
Martin Philips indicated that what I want cannot be done right now with
UniBasic.
--Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Rotella, Leon M.
Sent: Wednesday, July 25, 2007 2:54 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [u2] : Cleaner Case Statement
Just to be different...
Why not add a new label called Check.2 put it right before the label
Check.B
Then the code would look like:
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' ; gosub Check.B
case Ans = '2' ; gosub Check.2
case 1 ; gosub error.condition or null
end case
This would help from a maintenance standpoint, if later on Check.2
needed it's own code differing than Check.B
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave Davis
Sent: Wednesday, July 25, 2007 1:22 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [u2] : Cleaner Case Statement
Not good if answer is not limited to one character wide.
Isn't ON GOSUB out of style?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Manu Fernandes
Sent: Wednesday, July 25, 2007 12:44 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] [u2] : Cleaner Case Statement
Try this
ON index('AB2',Ans,1) GOSUB Check.A, Check.B, Check.B
Manu
- Original Message -
From: Brutzman, Bill [EMAIL PROTECTED]
To: u2-users@listserver.u2ug.org
Sent: Wednesday, July 25, 2007 5:48 PM
Subject: [U2] [u2] : Cleaner Case Statement
How can this structure be cleaned-up?
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' ; gosub Check.B
case Ans = '2' ; gosub Check.B
end case
The following is more difficult to read.
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B' or Ans = '2' ; gosub Check.B
end case
I would like something like...
begin case
case Ans = 'A' ; gosub Check.A
case Ans = 'B'
case Ans = '2' ; gosub Check.B
end case
so that the gosub Check.B command is not repeated. I have tried a
few alternatives without a victory.
Suggestions would be appreciated.
--Bill
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [u2] : Cleaner Case Statement
From: Clifton Oliver Execution should flow top to bottom, not left to right, from a comprehension viewpoint. Comprehension contributes to Maintainability, the premiere attribute of software quality. Along same lines, each case block should test the same sort of thing. Don't get sneaky for efficiency's sake. (Note: Efficiency Maintainability are often in tension.) E.g.: You are sorting cobras, bugs, garter snakes, lizards, rattlesnakes. The 2nd method below increases your chances of giving this to a junior programmer, an important consideration when sorting vermin. Don't do this: begin case case legs = 6 ; bug case legs = 4 ; lizard case red stripe ; garter snake case hood ; cobra case rattles; rattlesnake end case Do this instead: begin case case legs = 6 ; bug case legs = 4 ; lizard case legs = 0 ; * (snake) begin case case red-stripe ; garter snake case hood ; cobra case rattles; rattlesnake end case end case cds --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] Cleaner Case Statement
Personally I like the match or index syntax.
case ans match 'b':@vm:2 gosub checkb
case index('b2',quote(ans),1) gosub checkb
I also continue to feel there is a very good case for subroutine indirection
which would give:
sub = 'check':ans
gosub @sub
Use Case Ans matches 2]B, using the MV separator between the 2 and the
**
This email message and any files transmitted with it are confidential and
intended solely for the use of addressed recipient(s). If you have received
this communication in error, please reply to this e-mail to notify the sender
of its incorrect delivery and then delete it and your reply. It is your
responsibility to check this email and any attachments for viruses and defects
before opening or sending them on. Spotless collects information about you to
provide and market our services. For information about use, disclosure and
access, see our privacy policy at http://www.spotless.com.au
Please consider our environment before printing this email.
**
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] [u2] : Cleaner Case Statement
Hi Karen
I've seen this used in after prompt subroutines, where there were literally
multiple hundreds of Subroutines to execute, based on the attr number. In
that case it's cleaner, and might I add easier, than HUNDREDS of lines of
code that just say
CASE ATTR = 1
GOSUB 1
SNIP 400 LINES OF CODE
CASE ATTR = 202
GOSUB 202
SNIP ANOTHER 200 LINES OF CODE
CASE ATTR = 302
GOSUB 302
Granted, you end up with multiple ON .. GOSUB statements because there
is a limit to how many GOSUBs you can have on one statement, but to have few
statements instead of 600+ lines of code *just for the control statements*
is 'better', imho.
Of course one could conceivably write a small program to generate the case
statements, and you wouldn't have all the typing to do, but I still think
the ON statement has it's place.
fwiw
Allen
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Karen Bessel
ON GOSUB..Bad. Bill, that is a bad coding practice -
don't go there.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Manu Fernandes
Try this
ON index('AB2',Ans,1) GOSUB Check.A, Check.B, Check.B
Manu
snip
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
RE: [U2] : Cleaner Case Statement
Martin: Thanks very much indeed. --Bill -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Martin Phillips Sent: Wednesday, July 25, 2007 12:38 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] [u2] : Cleaner Case Statement Hi Bill, Unlike languages such as C, Basic does not allow multiple conditions in the way in which you are looking to do. In terms of run time performance or program size, if it really is just a GOSUB, there whould be little disadvantage in writing the more verbose form of your first example. Martin Phillips Ladybridge Systems Ltd 17b Coldstream Lane, Hardingstone, Northampton, NN4 6DB +44-(0)1604-709200 --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
[U2] Another gripe about IBM not letting end users access the articles in the knowledge base
We have a great VAR, we seldom need them but when we do they come through with flying colors but even they can not get IBM to get us an ID to access this. I am posting the response I've gotten from our VAR on this issue. They have tried to get us access to the locked articles in the knowledge base with this response from IBM. have emailed IBM U2 support on this several times, they have never been able to tell me how to setup an additional IBM ID for a customer. Throws the lack of support right back to IBM and points out the failure of IBM to address their paying customers and VARs needs. This is a problem that needs to be address to facilitate growth in the U2 market. Brenda Price Affiliated Acceptance Corporation Sunrise Beach, MO --- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
Re: [U2] Re: Move data files from Unidata to Universe
i like this idea! I may play around with it tonight ( I don't have data
to move around but I could create a file in unidata and try this idea)
results to follow ..
dougc
Stephen O'Neal wrote:
Another response from U2 Lab Services...
You could use the BASIC programs in UniVerse to make files in loadfile
format from the UniData files, and simply use loadfile in the uv/bin
directory to populate the UniVerse files with the data.
If UV and UD are on the same machines, the BASIC program could write to a
named pipe on the UD side and direct loadfile to read its input from the
named pipe. Then you do not need disk space for an additional interim
copy of the data.
Happy Hot Summer, everyone! Can you barbecue?
Steve
Stephen M. O'Neal
U2 Lab Services Sales Specialist
Information Management, IBM Software Group
Scott Ballinger [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
07/24/2007 06:10 PM
Please respond to
u2-users@listserver.u2ug.org
To
u2-users@listserver.u2ug.org
cc
Subject
[U2] Re: Move data files from Unidata to Universe
UPDATE:
Here is a response I received from IBM:
Scott,
I have checked with our Lab Services (aka consulting) group and they tell
me that there have been no requests to migrate a UniData account to
UniVerse, and there are no native utilities within UniVerse to do this.
They are willing to discuss this with you as a billable engagement.
FYI, if this had been the inverse .. migrating a UV account to UniData, it
would have been no problem, as UniData comes bundled with a command called
UV_RESTORE, which takes a uvbackup sourced account and restores and
converts it to UniData file formats.
So perhaps there is another way to skin this cat. Is there a way to
read/write to UDT files directly from UV?
Any and all off-the-wall, out-of-the-box, out-of-left-field, {insert your
favorite left-brained-business-creativity-MBA cliche here} suggestions
welcome.
/Scott Ballinger
Pareto Corporation
Edmonds WA USA
206 713 6006
On 7/23/07, Scott Ballinger [EMAIL PROTECTED] wrote:
I have a Unidata demo on my pc that I installed along the the PE version
of Unidata. I want to test in my Universe/Linux environment. How does
one
convert a Unidata account to Universe? (I am ok with the ud style dicts,
so
I just need to convert the data files, indexes? etc.) It has been
suggested
that uvbackup can do this.
/Scott Ballinger
Pareto Corporation
Edmonds WA USA
206 713 6006
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
--
When you are SURE that everything in your program is correct
AND your program STILL DOES NOT work, one thing you can be
sure of is that something you are sure of is wrong
- unknown
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
