This is a question about displaying line numbers in your VBA or VB code. I was reading all the threads, questions, and answers from years ago that appeared under related threads. I was hoping that there might be an answer now, because some of the answers from 2007 were not very nice, or intelligent.Why want line listings? Because it makes error resolution easier and because its common freaking sense. Which explains why it's not available in the VBE.
I don't know if I'm allowed to respond to this because I got in trouble for replying to someone before. But hey, GIVE ME A COPY OF THE RULES IF YOU DON'T WANT ME TO BREAK THEM, PLEASE!!! I mean it, I don't have a copy.
Since this is a general topic, maybe it is okay. I have to agree with the user chazw from 2007 here, which happens to be the opinion of the rest of the professional world. I'm not sure why the "experts on this site," who are supposed to be answering questions in this forum to help us, are turning this topic around on US and asking "why do you need to know this?". Is it because they do NOT know? Sorry, it seems like that is the case.
If/when you are actually EMPLOYED as a programmer (which I'm starting to think the people answering the questions on this website don't have experience with!), you have to attend "code review" meetings to get your code reviewed and approved by a team of peers, experts, and supervisors. This team is usually 10 - 14 people for me. They ask questions and bring up discussion points, based on the LINE NUMBER in the piece of code. Literally.
For example, a Scientist (person #8) in my meeting might say, "In line 4910 you set the time for the satellite instrument # 5, the Humidity Measurement for Africa (HMA), to equal Coordinated Universal Time (UTC) + 35 leap seconds = Temps Atomique International (TAI). Leap seconds do currently = 35 seconds. They are determined and maintanined by the International Earth Rotation and Reference Systems Service (IERS). That part of my code is correct. UTC + leap seconds (35) = TAI.
However, the Scientist points out an error in my code, that instrument # 5 (HMA) should be using UTC + 16 seconds = Global Positioning System (GPS).
All time in space is displayed in seconds since EPOCH. EPOCH simply means a reference time, NASA always uses the exact launch time for EPOCH. So EPOCH = 00:00:00 and the exact number of seconds that have passed since EPOCH are calculated, converted to bits, hexidecimals, added to 00:00:00, and then converted to a real time. What is the time?
My question is why should I look through 150+ pages when I could flip through to the line number. Furthermore, why should the higher level executives lack a way to describe exactly where their concern is located? I hope you can see, the material of the program is complicated enough, we don't need to add extra complication by having no line numbers.
All I can say is that NOWHERE on your website did I find instructions on how to put the line numbers into VBA for Excel 2007. If there is NO WAY to accomplish this, then the "experts" should say so. Don't insult the users by asking why they need to do it. That is bad customer service, dishonest, and wrong. Why can't you just admit that you don't know how to do it or that it's not possible. My guess is that the people writing the answers are completely UNEMPLOYED in software and they have been their whole entire life. Maybe they have a nice paper route, and play with LOGO as a hobby.
Sorry to bring you into this chazw, you had nothing to do with it except providing me a good launching point for my opinion.
If I am in trouble, I look forward to hearing about it.