It's tough to discuss solutions without getting slammed for
solicitation. My passion and business happen to be the creation
of unique solutions. That's what I'll talk about here but I will
offer to take continued discussion off-list. If someone is
offended by such things then feel free to stop r
Is anybody running EasyLabel with a UniData ODBC connection?
I'm running UniData 6.0.8 on AIX 4.3.3 unix system.
I'm trying to get EasyLabel 5.8.0.1282, on a winXP-PRO sp3, to use ODBC and
connect with UniData.
I have already created the UCI, and setup up definitions with VSG. I have
other to
Brian:
Of course, it'd be nice if the dbms would log happenings within its own
environment, like a UniData BASIC runtime log. It's a pain for regular
folk to have to build such basic functionality within the dbms (or step
through such hoops to get this basic information). :-)
Bill
Brian L
Tony,
Does it need testing for accessibility?
Thanks,
Dave
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Tony G
Sent: 05 December 2008 12:16
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] DEBUG mode on a UniObjects connections
You guys are descri
You guys 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
Spectrum is available from www.intl-spectrum.com.
Several list members write for the publication, and the editor is the previous
host of this list.
You can download back-issues in pdf format.
Brian
Brian,
This sounds like a good approach to me. I've recently written a phantom
launcher which as
Brian,
This sounds like a good approach to me. I've recently written a phantom
launcher which as part of the gui client, and whilst the phantoms it
launches generate their own logs, it would be nice to have a gui program
which told me what was going on. Sometimes a phantom hangs, and you
haven't go
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 the
These are all good approaches, but the difficulty is often in trying to
collate the information on what is happening client side and server side:
that usually means poring through multiple log files, especially if you use
different client languages as we did in my last company.
Our approach wa