>Over the years I have encountered many "standards" for namd and address fields in other systems, and designed many of my own. The desing can vary both in terms of hoo addresses are broken into fields, and the sizes of the fields. For example, in a simple case, one could have Address1 C(30), Address2 (C30), or maybe they should be 35 characters long, or maybe 40 for long addresses. In some cases we may decide to break out the numneric portin of the street address as StreetNumber C(10), AptNummber C(10), StreetName C(30).
>
>Names may be broken into first and last, or first, initials, LastName.
>
>Emails could be c(40), or maybe this isn't long enough and we need C(70)- so what should the right length be?
>
>I would be interested whether there are published guidelines for this - especially in deterermining the optimum lengths so as to be able too hold typical data without making fields too long.
I don't know about standards, but note that you can use a memo field to avoid wasting unneeded space. You will still have problems in reports, if you don't reserve enough space.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
