Benjie,
Unfortunately you will occasionally run into an issue like this. Problems with opening TAFs made with 5.5 are very rare and we feel we have a good level of backwards compatibility with 5.5. As you get older, however, more and more bugs in the old Studios have created TAFs which are out of spec. The 5.5 Studio, which was an evolution of that code, had hacks in place to handle most of those issues. TeraScribe v6 is a brand new codebase and conforms to the TAF spec. First suggestion would be to use the very latest version of 6.x. We have made backwards compatibility corrections as we’ve encountered them through the product’s lifecycle. Second suggestion would be to first open and save TAFs and TCFs in Witango 5.5 Studio. Third suggestion would be to watch out for problematic actions. One of note is if ALL of the Select columns in a search action are custom columns, the custom column syntax has changed over the years and this situation is not handled well by TeraScribe. In all of the cases that I’ve seen so far (only 2 or 3), fixing the corruption has come down to deleting and recreating a few actions. If you do find a repeating pattern, feel free to email both the original TAF and the TAF post open/save in v6 with some information about the corruption to support@ and I’ll see if there is anything that can be done in the code. Robert From: Benjie Castro [mailto:bcas...@oxy.edu] Sent: Wednesday, February 19, 2014 6:43 PM To: TeraScript-Talk@terascript.com Subject: TeraScript-Talk: file is corrupted after editing with Developer version 6 We recently migrated to Witango 6 server and started using Developer version 6. We have one program that got corrupted after editing it with Developer version 6. We have used Tango Developer 2000 (version 4) previously and those programs edited with that version work without any problem in Witango 6 server after migration. We have only edited a couple (at most 3) of our programs using the Developer version 6 and have only found one program to be corrupted so far. We are afraid that when it's time to edit some of our programs that they will get corrupted too. Any ideas on how we could avoid our programs getting corrupted after editing with Developer version 6? _____ To unsubscribe from this list, please send an email to lists...@terascript.com <mailto:lists...@terascript.com> with "unsubscribe terascript-talk" in the body. ---------------------------------------- To unsubscribe from this list, please send an email to lists...@terascript.com with "unsubscribe terascript-talk" in the body.
