Perhaps make the two conditions and make them part of the same conditional? e.g.

if ((life == ToBe ) || ( life != ToBe ))
return Question;

CaptJosh There are only 10 kinds of people in the world; those who understand binary and those who don't.

I have to say, my tendency would be to have a list of the known postal codes and put that into an array. Then use a string compare to just look for matches to all known postal codes first. Then after that start doing evals to look for things that fit the known formats but aren't on the known list, if possible, presuming each entry is a separate line or item in an array, only putting the lines or items that haven't already matched into a separate array and checking those. Not sure if my solution is more or less complicated. It's probably colored by my experience as a LAMP dev though.

CaptJosh There are only 10 kinds of people in the world; those who understand binary and those who don't.

Hrm. I seem to have baffled the boards...

CaptJosh There are only 10 kinds of people in the world; those who understand binary and those who don't.

This is is not what I was thinking of. Let me describe exactly what I'm working with on the project file. I right-click on the project in the sidebar after loading the solution. I click on properties from the popup menu and get a pop-up window of project properties which also has a sidebar. I click on "Linker" in the sidebar and the first field in the main area that shows is the Output File field. There I can change the filename. Is there anything I can enter in this field to make it automatically include the compile date in some form in the filename?

CaptJosh There are only 10 kinds of people in the world; those who understand binary and those who don't.

I'm trying to find out what strings to enter into the output filename field of the linker section of project properties in order to make my project always have the compile date included in the output filename. Preferably year first, then month, then day, as this will make the numbers increment more logically. Separators such as hyphens or underscores between the numbers are acceptable, but not necessary. The idea is that the compile date can act as a build number, and also will tell me at a glance which compile is from when, so I have an idea of what features are in the build based on when I compiled. I did try digging around in the help files, but as usual for MS, they should be called "no help" files.

CaptJosh There are only 10 kinds of people in the world; those who understand binary and those who don't.