joeware - never stop exploring... :)

I just wanted to touch base and let everyone know that admod v01.07.00 is still coming along. I have finally finished getting some additional debug logging into the tool in the event someone finds something that doesn’t appear to be working right and need to get me involved. This is necessary for some of the additional CSV capability which has some pretty involved logic strictly due to trying to back this logic into existing code that was never planned to have CSV capability.

I also ran into a stumper where running in debug mode something was breaking but running normally it works great. I didn’t realize I was hitting that as I usually run in debug mode when developing and don’t test in normal mode until everything is worked out. However I started to get a feeling I was hitting an odd problem I have hit before with this older Borland compiler.

Unfortunately admod and adfind are still using the my old BB6 Pro code and libraries so I have to deal with a couple of the older problems that are corrected in BDS2006 such as this weird debug issue. I have to go through an extensive conversion phase to get the old code to compile properly under the new environment (my fault not Borland’s) since I changed all of my libraries to more Unicode compliant code. I know moving admod/adfind would be a serious pain in the butt and it isn’t worth it to me for the old versions, might as well do it for the rewrites when I am already doing massive code reformatting.

So anyway, now that I identified that problem, I have moved on with my testing and things are looking good, now I get to start working on the part I really dislike…. Trying to document in the help/usage the new functionality and how to take advantage of it. This is not going to be fun for several reasons. The first being that I hate documenting this stuff since it isn’t for me as I don’t need it. Also because I basically invented a bunch of opcodes for specifying various transforms for the data for the CSV options and have to explain each one and how each is used. I also have to explain how the CSV stuff works which especially for the MODIFY options is a little involved. As mentioned before, I know why CSVDE is an ADD only tool now, modify is challenging with CSV format. Don’t believe me, right a script to handle it. How do you specify a delete of a single value or the whole attribute or replace a multivalue attribute instead of add to it… There just isn’t enough info in the CSV format to do much more than Add. So in order to allow modify, users get to type some challenging command lines to explain their intent and that is just to allow replace/add. I am still up in the air if I will allow value or attribute deletes through CSV yet. I am leaning towards no.

  joe