I'm not sure how easy this will be. If you look at the line were it won't compile, and that line is within the actual property definition, you can change that by using custom code from within the BO mapper. However, it is bombing in the field enum or field names array or field descriptors (the ones I remember) that also get generated by the BOMapper using the column names, then you're likely in trouble.
A common solution is to build a view that has better field names, make it updatable, then use it to build your BOs and then access our data via that view from the BO.
Other options might be to use the view to build the BO (via the BOMapper), then provide sprocs for data access. Fill methods would need to alias renamed columns so the BO's underlying datatable had the correct structure. The view wouldn't need to be deployed for app to work (just used to get BOMapper to work).
You could also user the DDT (Data Deployment Toolkit) to build the structure and build the BO and use sprocs to handle data access (add, edit, delete).
I'd be happy to explore these options in more detail if needed (as other would I'm sure). Just keep asking the questions!
