Fred,

You know, the strange thing about this Excel/zipcode bug is that the work around is to export the Excel worksheet to an ASCII text file and then Import that into the .dbf format. EXCUSE ME but isn't exporting to ASCII converting that zipcode column into a text field? I just don't get it sometimes. They are saying, in effect, "We can't convert zipcode formatted columns to a character field so what you'll have to do is use Excel to convert the zipcode column into a character type field first". Enough said, my blood pressure is rising to dangerous levels.

About "New England"; you are probably not aware of it but I'm from Texas. Around these parts the phrase "New England" is a generic term meaning "up north somewhere" usually referring to anyplace north of Tennessee and East of Illinois. For instance, in the sentence "Bubba's done moved to New England", the speaker means that Bubba moved up north somewhere in which case polite society will no longer mention Bubba's name in mixed company.

The local Indians also use the phrase as a generic term meaning "land of cold" and they shiver when ever they say it.

If you have ever had problems with mail delivery from down south, you can see were the problem gets it's origins. If Dell, for instance, is sending a computer to New Jersey, the southern postal worker will see the New Jersey address and, realizing that it is going "up north somewhere", will put it in the bin marked "New England".

Anyway, enough of this idle Sunday morning chat, I need to get back to work engineering more work-arounds.

Ed

>I think Microsoft talks their way out of too many problems with "by design". Why don't they just admit it, it's a bug, whether the "design" was incomplete or not? Even if it is "by design", they should do a much better job of documenting those shortcomings. PS, 07xxx is a New Jersey zipcode (along with 08xxx), but I think they'd be surprised to find out they're in New England. :)
>