11/26/2024 8:26:09 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss writing script in Architect plugins for SalesLogix & general SalesLogix customization topics (for Windows client only). View the code of conduct for posting guidelines.
|
|
|
|
Setting up Debug Enviroment
Posted: 08 Aug 06 10:01 AM
|
fiogf49gjkf0d A bit off topic, sorry. I've been working with a tree view and it has a nasty loop. I know if I can get it into debug (Vis Studio2003) I'll be able to figure it out but I cannot get the debugger to activate. I've set my client to debug "On Error" and put a "break" statement in my script right before the While statement that is looping. If I comment out the While the script does not fail. If it's active it'll lock up the SLX client (CPU at 50%).
If anyone can help me figure out how to setup my debug enviroment I'd appreciate it greatly. After that I should be able to figure out my problem.
Thanks!
Marc A. Johnson
Network Administrator
Optimum Solutions, Inc.
615-329-2313 x2240 office
615-329-4448 fax
mjohnson@optimum-solutions.com
www.optimum-solutions.com
Your only payroll, HR and time & attendance solution. |
|
|
|
Re: Setting up Debug Enviroment
Posted: 08 Aug 06 10:03 AM
|
fiogf49gjkf0d Marc,
You can try two things.. Change the SLX option to Debug on everything and wait for it to pass through.. or..
Can't you use the "Attach to process" from inside VS and attach to the SLX process before you generate the error then generate the error and see what happens..?
|
|
|
|
Re: Setting up Debug Enviroment
Posted: 08 Aug 06 10:09 AM
|
fiogf49gjkf0d Setting to debug on everything got the debugger to open. I was finally able to see that i didn't set one of my variables correctly. I thought Option Explicit was supposed to prevent undefined variables from being used?
BTW, once this error was overcome the "On Error" started working. So there isn't a problem with my debug enviroment. Thanks! |
|
|
|
Re: Setting up Debug Enviroment
Posted: 08 Aug 06 12:39 PM
|
fiogf49gjkf0d Try adding a "stop" statement ("break" won't trigger the debugger to fire). When your stop statement is reached it shoudl automatically fire up the debugger as long as it finds one located on your machine.
Also, if the look is locking up the client, I would guess that there is no condition for it to end the loop (ie: an endless loop). Post the code here and we can take a look with you if you want. |
|
|
|
Re: Setting up Debug Enviroment
Posted: 08 Aug 06 12:57 PM
|
fiogf49gjkf0d Ryan,
Thanks for the "stop" tip. I'm not a coder by trade so I sometimes forget my syntax. As for the code, I found that it was a non-defined variable problem. I was executing a SQL statment and storing it in strSQL, but I defined srtSQL. So my statement went to limbo. My While statment was looking for an EoF for a non-existant record set, thus the loop. |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|