Redefine the LOCATION CODE table used by the Volunteer Module

So instead of having just one field to hold concatenated values of address + city + state + zip, it would  have separate fields for those values <3 fields for address lines would be great!> - We "play-loaded"  this table with data
but first had to concatenate address fields together before it would even load and afterwards
some data got truncated due to length issues. Also would suggest making this a config table (similar
to what was done for the LOCATION table in the BBEC Events module) instead of a code table -- Seems odd
to use address data in text string format for data validation purposes

  • Guest
  • Nov 24 2015
Organization Name (Please enter full organization name) The Ohio State University
Reported Version 4.0
  • Attach files