Adding settings for the user to have to set complicates things (decimal point and field char) for them, their are often far better ways really (though not always), you can auto-detect what the file is using (by doing a quick scan of the lines in the file for one), but at the moment I've gone the easy route and set the CSV load/save functions to use the users machine locale setting.
I will ALWAYS avoid adding any unnecessary settings for the user to have to set/fill-in if at all possible as it gives them something else to set/get wrong and cause problems.
Never let your PC software generate exception pop-up boxes on a users PC, if it does (as your CSV code was doing with the range check error exception dialogs) then the code must be fixed to never do so (you can totally screw up a PC if it gets out of hand if your software decides to throw up a 100 exception boxes in the following 2 seconds - I've had that happen and learn from it). Always assume the user is going to load a totally incompatible file (because they will at some point), always do sanity checks on every part of the data you're loading in, if their seems to be a problem with the data then let the user know so that they can either fix the error they are making or get back to you with the much needed feedback for you to fix the source coding error - treat pop-up exception dialogs as evil ;)
