September 13, 201411 yr As I tried to wrap my head around the idea of expanding the database limits, I keep coming back to the idea that we'll need a new database editor. MS Access is getting long in the tooth so a wholesale re-write might be nice. Well, the database storage mechanism will be a whole lot different so how do existing battlesets and scenarios get treated? Maybe their databases could be migrated to the new format. That train of thought led me to digging in old source code (from HC2002 actually) to see what Tools Bret had to dig information out of the legacy battlesets. It turns out he had a tool that exports any legacy battleset to the .csv files we are familiar with when using the platform editor. That was a big surprise. Even more was noting that he was already working on the code to take the .csv files and stuff them back in to the battleset.res files. That code needed some work but I just got it into shape (for Original GIUK anyway). Note the successful edit of database information!
September 15, 201411 yr Hurrah!!! (I understand correctly that can drive to a new DB editor without some 2000 ítems limit?).
September 15, 201411 yr Author (I understand correctly that can drive to a new DB editor without some 2000 ítems limit?). No, this is just a very first step in the direction over breaking through the 2000 item limit, developing utilities to export the legacy databases such as Original GIUK. Speaking of which, more progress. It now allows editing and exporting of all of the traditional annexes.
April 17, 201511 yr Heck, I'd just like to have access to the tool to *see* the flags and such on the old DBs, not necessarily to edit them. If I want an up-to-date DB that can be edited as time goes on, I can use the current modular setup. However, to be able to know what a/c can fly vlow, what missile min/max alts are, etc are info I'd love to know. Also, various base defenses.
Create an account or sign in to comment