Good idea to have a flag if the error should be logged: if you have
several logs (eg 1 for user, 1 for tech stuff), it would be good to
say just where it should log.
Also need to be able to pass data to show in the message: eg Customer
not on file.
Perhaps pass up to 3(?) parameters which c
Universe System(9001) is supposed to be the equivalent of Unidata System(49)
W
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
I get it with:
IF LOC = "" THEN
LOC = SYSTEM(49)
NUM.LOC = DCOUNT(LOC,@AM)
LOC = LOC
LOC = "/ud/":@WHO:"/":LOC<1,2>:":":LOC<1,3>
SWAP "/_" WITH "/" IN LOC
END
On 2/9/2011 6:36 PM, Bill Brutzman wrote:
Is there a way to capture the name of the program, sub, and current line of
UniBasi
The UniVerse server may have cached the decommissioned DC server name.
At a command prompt on the server try clearing the remote cache name
table (nbtstat -R).
Andy
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Hol
SYSTEM(9001) in UV I think.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of David Wolverton
Sent: Thursday, 10 February 2011 10:46 AM
To: 'U2 Users List'
Subject: Re: [U2] Clear Message Initiative - Logging Errors to
In UniData we can get that from a SYSTEM(49) I think.
-Original Message-
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Bill Brutzman
Sent: Wednesday, February 09, 2011 5:37 PM
To: U2 Users List
Subject: Re: [U2] Clear Message Initiati
We're running UniVerse on Windows server 2003, the users are validated
against AD and use the home path in AD to match up with the Universe
Account. When we shut down or original DC (we have two that are
properly replicated on site) users can no longer log into Universe.
Everything works properly
Is there a way to capture the name of the program, sub, and current line of
UniBasic code?
For example, the user at the Dock tries to ship out a quantity of of parts more
than are in the inventory bin location. The UniBasic program calls a sub to
splash an error message to the user's screen, a
I have implemented a system that leverages syslog-like logging, and the
ability to adjust log levels in realtime without recompiling the
unibasic code.
I am using pythons logging module with a configuration stored in /etc.
The verbosity of logging can be configured per program without recompi
Any other suggestions for multi-language?
On 10 February 2011 11:16, wrote:
>
>
> Here's the problem I see with moving messages out of the code.
>
> It's perfectly fine *if* you have a developer environment of some kind that
> automatically pulls in messages while you're reviewing code. Howeve
I can agree with that of course.
I've implemented systems that are architecturally beautiful and easy to
maintain :)
I was just pointing out that in my experience, this sort of shifting material
out of in-line code makes the system harder to maintain not easier.
There are many people who have an
That only holds if you have implemented it wrong. Spend some time to
think about how you would implement it.
1. Have a subroutine/function which handles the error. That is, it
displays it as appropriate, as well as logging details as required. You
pass it an error number and optional text for the
Here's the problem I see with moving messages out of the code.
It's perfectly fine *if* you have a developer environment of some kind that
automatically pulls in messages while you're reviewing code. However in my
experience, very few sites have anything close to this.
As the next one to co
The trouble is, it's so much easier to
Just code
"... ELSE CRT @(00,24):'***ERROR*** end date must not be before start
date' "
Than
Now code
" ... ELSE ErrorCode = '123456'; ErrorText = ''
CALL ErrorLookup (ErrorCode, ErrorText)
CRT AtErrMsgPosn:'***ERROR*** ':ErrorText
This is indeed an excellent article. Thanks, Susan! Error messages
certainly get ignored, and I'm as guilty as rest.
Charlie Noah
On 02-09-2011 2:02 PM, Bill Brutzman wrote:
Thanks to Susan Joslyn for the excellent article on the "Clear Message
Initiative. I just received my copy of the mag
Another thing we plan to do with messages some day is to set them up
in a messages file, so different languages can be easily handled.
It would also be nice to be able to maintain the message without
program change - makes sense.
On 10 February 2011 09:02, Bill Brutzman wrote:
> Thanks to Susan
Thanks to Susan Joslyn for the excellent article on the "Clear Message
Initiative. I just received my copy of the magazine in the mail today.
It happens that over the weekend, I was reading "Code Complete 2" by Steve
McConnell of Construx. Following an idea in Code Complete...
Yesterday, I to
No, I am wrong regarding the SUBROUTINE. On a second read, it is referring to
the name of the called routine and the possible three places where a match
must occur.
Sorry about that.
DavidJMurray (mvdbs.com) wrote:
>
>
> Interestingly enough, this is also implied in the SUBROUTINE
> documenta
Dan,
That makes sense. Something was nagging me from the back of the brain; I
think that I was getting confused between the CALL and SUBR statements.
I often used the SUBR function within UniBasic as it can be interchanged
with FUNCTION definitions etc; which enables a write-once, use everywhere
19 matches
Mail list logo
