Is it possible the DB column was renamed in the program, or not in scope?
Another gotcha I've seen is quotes in my expression around a numeric literal. If the variable is numeric, don't put quotes around the literal. If the variable is char, then you need quotes around the literal.
-----Original Message-----
From: Terry Hertel [mailto:T.Hertel@xxxxxxxxxxxxxxxxx]
Sent: Tuesday, November 27, 2018 6:27 PM
To: wdsci-l@xxxxxxxxxxxx
Subject: Re: [WDSCI-L] Debug
When I took the conditional expression off the breakpoint, the program was stopping at the breakpoint, but the record I need to debug is thousands of cycles. I re-added the breakpoint conditional expression but instead of using the database field I used the input parameter for the sub-procedure because I noticed that the database fields were not visible in the Variables tab but the input parm was. That worked fine.
Terry Hertel
Programmer/Analyst
Peerless Industrial Group
A Kito Group Company
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
