Tony,
I think you are right.
Since all our routines take three parameters, InPar, OutPar, and
ErrStat, we have a routine which can be run as part of a telnet session,
thus decreasing the likelihood of a routine crashing when called from
VB. Ordinarily, what I'd do is run this program, and call
with the desired message. We have a global common
flag
to toggle it on/off or output to screen, as well.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave Reynolds
Sent: Friday, 5 December 2008 1:23 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2
are describing a new product I've been developing as
time permits:
removepleaseNebula-RnD.com/blog/tech/mv/2008/09/remotecontrol1.ht
ml
Tony Gravagno
Nebula Research and Development
TG@ remove.pleaseNebula-RnD.com
From: Dave Reynolds
Brian,
This sounds like a good approach to me. I've recently
Hi all,
I'm new to the list, and hope that someone may have the answer to a
problem which is causing me a lot of headaches at the moment.
I'm using VB6 and UniObjects to connect to a Universe Database.
I call DataBasic routines from the VB6 client.
All works fine, until there is a problem in
Hi Brian,
Wrong answer(Grin).
If I run the same thing under JBASE, and it drops into DEBUG, everything
is fine, and I can even step through the program a line at a time.
Oh, well, back to the drawing board. I wonder if I could use Process
viewer to see what is happening.
Many thanks for your
a debug statement in the code. You need to find it and
get
rid of it, it should not be in live code, and will certainly not work at
all
with a uniobjects call.
Rgds
Symeon
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave Reynolds
Sent: 04
Brian,
Interestingly, I have just nocked up something using a demo f MVdotnet
which uses Core Connections. This opens a session window when I go into
DEBUG, and I can perform all standard dEBUG commands. The only slight
problem is that all our software is written using UniObjects, and I am
it
and get
rid of it, it should not be in live code, and will certainly not
work at all
with a uniobjects call.
Rgds
Symeon
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Dave
Reynolds
Sent: 04 December 2008 10:10
To: u2-users
Interesting idea that.
As standard, all subroutine calls in our software add to a Stack and
their names are deleted from the stack when control is returned to the
calling level. It doesn't solve the debug issue, but has given me an
idea about tracing. I'm sure the code was originally designed for
