Brett, I entirely agree with you, and if humanly possible, I'd rather not go into DEBUG at all. I even have a test bed for routines, which can be run in a telnet session, so that by the time you get to the point where you are calling it from VB, all errors are ironed out. But you know how it is...
Thanks, Dave -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brett Callacher Sent: 04 December 2008 13:22 To: 'u2-users@listserver.u2ug.org' Subject: Re: [U2] DEBUG mode on a UniObjects connections Agreed with COMO comment. Depending on your version of Universe you may also be able to: 1. TANDEM to the UniObjects port. This should enable you to interact with the debugger. 2. See any errors produced by looking at the runtime error log (create a file called errlog in the uvhome) In general it is better to prevent any routines called via UniObjects from accepting any input. It is preferable to try and return an error condition to the caller. HTH Brett "Allen Bell" <[EMAIL PROTECTED]> wrote in message news:<[EMAIL PROTECTED]>... > When I have a problem like this I usually put a COMO ON statement near > the top of the program and the look at the output stored in the &COMO& > file. If you have a bad line of code that causes the abort or debug you > can see what you would normally see on the screen if you were using an > interactive connection > > EXECUTE 'COMO ON {substitute some random name here}' > > > Regards, > > > Allen > > Symeon Breen wrote: > > Databasic will only go into debug mode if you tell it to - this is done > > either at the command line or with a debug statement in the code. Since you > > are calling the sub from uniobjects it will not be a command line issue so i > > suspect you have 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 December 2008 10:10 > > To: u2-users@listserver.u2ug.org > > Subject: [U2] DEBUG mode on a UniObjects connections > > > > 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 the databasic code, which > > sends it into DEBUG. > > > > The client screen locks up, and my talking screenreader goes into sulk > > mode, which normally means I have to reboot. > > > > I wouldn't expect anyone on the list to solve the screenreader problem, > > but sighted colleagues have reported similar experiences with this type > > of connection. > > > > Is this a bug in UniObjects, or did I set it up wrongly. > > > > Many thanks for any ideas, > > > > > > > > > > > > > > > > Dave > > ------- > > u2-users mailing list > > u2-users@listserver.u2ug.org > > To unsubscribe please visit http://listserver.u2ug.org/ > > No virus found in this incoming message. > > Checked by AVG - http://www.avg.com > > Version: 8.0.176 / Virus Database: 270.9.12/1821 - Release Date: 03/12/2008 > > 17:41 > > ------- > > 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/
