What tool to use for bulk DBC edits

[Darkon47]

I have been revamping first aid into another profession on my server, doing so requires large amounts of DBC edits and I need to add 200+ spells to my server for the recipies, 180 of these are formulaic and I had hoped to do this by converting the DBC to a CSV, adding lines to that with a small Java program, and then turning that CSV back to a DBC. However the DBCutil that I tried using corrupts the CSV produced from Spell.DBC preventing me from turning it back into a DBC without destroying all strings, and potentially more than just that.

Basically what I am asking for is what utility I should use to either convert the DBC to and from a CSV or the like, or a tool i could use to make a patch to add more lines to the DBC from a CSV or other simple format file.

[Chase]

Use OpenOffice to open the CSV, where everything is separated by commas, and the text separator is a "

If you are using Excel, Excel doesn't let you do this. (Funny how a free program is better than a paid one.)

[Darkon47]

Unfortunately open office caps the number of rows that it will open at about 50,000 and will not properly import anything with more rows than that, and the Spell.DBC has ~70,000 rows by default for a 3.3.5a server as mine is. Additionally it would not really help my problem, as I was looking to do bulk edits with formulaic variations in each one. I have a bit of Java code written to calculate the formulas, and I could use it to make a CSV fairly easily, i just need to find a way to append that onto my Spell.dbc

Edit:
Found out how to do it. The problem originates from the strings in columns 171 and 188, mostly for rogue finishers. To solve this without losing data, use version 1.2.2 or above of myDBCEditor to export the strings as a patch, then clear columns 171 and 188. Next save it as a CSV from myDBCEditor, append your edits to this file with your bulk editing code, then open that CSV with myDBCEditor once more, apply the patch you made earlier, and save it as a DBC!

Edit:
Apparently some flags get destroyed when using the DBC to CSV convention here. The ones I have noticed are any flags with letters in them, and any negative rows