Then again, almost everything comes at a price/cost. Especially good things. Rarely will you find something that is good and is completely void of cost of some kind. Anyway, in the case of Visual Age, would it not make sense to just agree ahead of time on a format. Or, if a team doesn't want to be going through all that hassle at the beginning, then once they bring together the code and find that there are formatting differences, they should just agree on a particular format and each team (or individual, whichever is the case) has to just change the preferences, hit Ctrl + W, and that's it.Hiran> Matt,

> Interesting that you brought up code formatters. I sometimes find that a tool that is supposed to "aid" development can cause more problems. I use Visual Age at work for my development, for my sins. Not only does it have a code formatter, it is customisable. If you want curly brackets on the same line, you can configure it. If you want them on to appear on their own lines, you can configure it. All it takes is a CTRL-W and all your code is nicely formatted just the way that you like it. This is fine, until you are working in a team development. Try doing a code merge where different developers have been making changes to the same section of code but use different settings. Personal choice is great, though sometimes at a cost.