Thanks for your help. I tried it, but that didn't work either. There were two files, as you suggested: .vbp and .vbw. I deleted the .vbw file and the annoying files quit appearing. Thanks again! JimT

modified on Tuesday, February 12, 2008 11:49 AM

I am condemned for my sins to write in VB 6 for the next several whiles. Every time I fire up VS and select my project the IDE is populated with five modules I have absolutely no interest in seeing, editing, running, or anything else. I have closed them and saved the project more than once, but there they are the next time I start up. Does anyone know where VS or VB saves whatever it is that makes these things appear? Better yet, does anyone know how to make them stop appearing? Thanx, JimT

My dad and my sister and I used to go hiking in the mountains along the Hudson above New York City. Took the compass only once. It kept pointing to the mountain full of iron no matter where we were. We learned to follow ridge lines or water when we were off the trail.

I recently bought an Edirol UA-25 USB audio interface. My laptop is now a recording studio. It's not hand held, but it is a great piece of gear. 96k 24-bit sample/sec, 2 channels. It's about the size of a paperback book.

VS2008 takes even longer... Now that's something to look forward to!

I was afraid it was coming to that. Sigh.

I performed the suggested ritual. VS still won't activate the OK button for anything but a File System location. Any other suggestions?

Ah, so! I will try the fix in your reference. Thanx!

I have IIS installed, but that doesn't mean it's installed correctly. I uninstalled it and then reinstalled it, but it didn't seem to make any difference. Are there tweaks I need to apply?

I am running VS2005 & .NET 2.0. Trying to create a web service in VB using the ASP.NET Service Application template. If I select "File System" in the Location box, everything works fine. If I select "HTTP" the OK button is greyed out so I can't create the app. Obviously, I am failing to do something I should, or doing something I shouldn't. Can somebody give me a clue?

This may be too late for your poll, but I just returned from vacation. In 1962 I was hired as a mathematician/physicist at a company that had a computer. I asked the resident programmer how to make it work. He handed me an IBM pamphlet that listed the statements recognized by the IBM 1620 Fortran with Format complier. I programmed out of that for several whiles before I found out there was a Fortran manual. By the time the company felt it worth while to give the engineering staff a formal course in programming, I was already using assembler (1620 SPS) to make changes to the Fortran compiler. Those were the days! The only in-depth programming courses I have taken were in C++. The best was a week-long session with Dan Saks. I have never written an application (or significant part of one) in C++. Daily work involves C# and VB. Sometimes I get to write in C. I write code to solve problems and make things work. I do my best to distance myself from the notion of IT and all its attendant buzzwords. I get my jollies writing language translators that convert unreadable glop in the "Someone's Great Idea" programming language into something that an "IT Professional" can cope with.

No! No! No! It's ________ADD ONE TO COBOL. (I had to put the underscores in to get it to start in column 8)

Fujitsu NetCobol.Net: http://www.netcobol.com/products/windows/netcobol.html

Michael, Back in ancient times (ca.1966) my friend Richard Pratt and I had a little contest, coding a binary search in IBM 360 assembler. At the end we were fighting to remove individual cycles from the loop. When we agreed he had won, reaching the irreducible minimum loop time, Dick Giering showed up with a faster method in hand. His algorithm wasted "lots" of time at the start building a halving table. Once he had the table built, his search ran almost twice as fast as our best effort, because he didn't have a divide instruction inside the loop. Don't feel bad. As the saying goes, "Ve get too soon oldt, und too late schmart." JimT

The interesting part is a) looking back at all the really hot new stuff that has just faded into the background when it turned out to be not so hot after all, and b) looking at the evolutionary durability of some of the cockroaches and dinosaurs that were supposed to be superseded by the aforesaid hot new stuff. I started coding in Fortran. I still write quick-and-dirty stuff in Fortran from time to time, although most of the time I use VB or C#. A friend of mine writes in COBOL.NET. My current project uses ASP.NET. In between I have used at least a dozen different assembly languages, macro translators, and procedural languages, plus a pile of graphical design tools. I have seen a lot of boutique languages come and go in that time. I can't even remember the names of most of them, even though they were surely going to be the ultimate tool at the time. Hardware has gone down in price from over $1.00/byte to 0.1 microbuck/byte. Speed has gone from 20 uSec/cycle on a machine that used 6 cycles per instruction to pipelined dual processors that run instructions in parallel at over 5 billion instructions per second. I missed the relay generation completely, and just got in on the tail end of the vacuum tube generation. The Fortran run-time package on the IBM 1620 occupied 400 6-bit characters out of a 20,000 character memory. I added line printer control to the package at a cost of 200 additional characters. When IBM added disk drives to the system the thing bloated up to 1400 characters or thereabouts. When we got a 360/40 with disks and tape the operating system grew to occupy an astonishing 6000 bytes. I started doing real-times systems with the IBM 1710, which was a 1620 with interrupts and analog and digital I/O. Now the power of that system can be yours for about $6. I could go on, but no one wants to listen to an old guy ramble.

I am working full-time as a developer for ChartLogic, Inc. We sell an Electronic Medical Office software package. My task is to build an internet-enabled thin-client version of the package so doctors can work from wherever they happen to be, without being tied to the LAN in the practice office. Lots of fun!

Kareem, My son is a manager for a company that creates military hardware and software. My grandson is a manager of a call center for a software company. My great-grandson uses his computer to play games. I just write code. Been doing it since 1962. Plan to keep on doing it. I'm 74. JimT

When I interviewed, the 1620 they showed me had paper tape input and output. By the time I reported for work they had removed the tape and added a card reader/punch. Hard copy was produced by running the cards through an accounting machine. We got a line printer a while later. The fun part was modifying the Fortran compiler and run-time package to work with the printer. Those were the days!

I'm 74. I got my only degree, in physics, in 1960. I have been programming since 1962, when I fell in love with an IBM 1620. In May 2007 I accepted a full-time programming position writing embedded systems software. As Shakespeare said, "The fault, dear Brutus, lies not in our stars ..." You can't lift yourself up by putting the other guy down.

Getting good repair work is easy. Depending on where you live, find a Mexican, Venezuelan, Cuban, African, etc. immigrant mechanic, anyone who learned his trade in a _really_ impoverished nation. I spent several months in Venezuela, where new cars are found only among the favored few. Everyone else has to keep his 20-year old car on the road by heroic measures. A mechanic who survives under these conditions has to know his job better than a "replace it and see if that fixes it" guy.