I can't debug my code in VB6 IDE

Question

Hi,

I'm trying to debug the code in VB IDE. This IDE is able to debug the console VB Scripts. But in our project, we are generating the HTML pages using the VB. We wrote the .cls modules for that. When I try to debug this .cls modules, the control is not going to the particular code line. All the properties of my project is alright. Please help me that how can I debug the code?

Thanks,
CLN Sharma

---

Suma

Answer 1

See here: Visual Basic 6 Questions.

---

Kevin

Answer 2

Thanks for your reply. But it did't help me.

---

Suma

Answer 3

I was urging you to try one of the VB 6 forums mentioned in that link. The MSDN forums are for VB .NET only. 

---

Kevin

Answer 4

I know this is old, but its threads like this that make MSDN forums suck. The op must dig through another resource to locate an answer he/she might not be sure about. As it turns out that link was absolutely useless, in fact it has cost 2396 people's time.

I am sure the goal of MSDN forum sites is to become a resource of knowledge, of answers, for years to come. With a link-only answer, the op must dig through another resource to locate an answer he/she might not be sure about. Most importantly, if your link were to ever break, your answer is useless for anyone who visits this page in the future.

Moderators and Microsoft employees consider un-marking any answer that does NOT have a solution. Imagine the SOAP for this problem:

Subjective

Cant debug VB6

Objective

The IDE is able to debug the console VB Scripts. But in a other project, user is generating the HTML pages using VB. When they try to debug the classes or modules, the control is not going to the particular code line.

Plan

Refer user to an blog post about that they will have to read to work out where to re-post their question

Action

User finds the link: http://social.msdn.microsoft.com/Forums/en-US/vbide/threads then cant be bothered, because the support here doesn't help!

---

Jeremy - MCP | MCAD.Net | MCSD.Net

Answer 5

The intention of my post was merely to inform the OP of Microsoft's instruction that VB 6 questions should be asked in the VB6-specific forums I linked to. The link wasn't intended as a direct answer to their question!

---

Kevin