I am trying to enter a sysex data string via the event view window, but each time a string is entered to move to the next line, previously entered data disappears?
I tried using the Sysex editor itself but for some reason it does not save to a midi file? 
 
Any ideas?
 
Thanks

Hi...I use sysex data to transmit cues to a lighting board.  I have found that if you have a sysex message that is too long that it will disappear until you click on it to edit it.  This is a problem for me because I like to see what lighting cues are coming up in the Sonar event list for sysex data as I play back music and midi data.  I also use Sonar event list changes (program numbers in Sonar) to run "snapshots" on a digital audio mixer.  Snapshots are stored configurations for the audio mixer much like cues for a lighting board.
 
Here is an acceptable length sysex data message: F0 7F 01 02 01 01 31 35 00 31 30 F7 and will be displayed in full in the event list for a midi track.  If you go beyond the 12 groups of hex code then the data will not be visible once it is entered.  However, it's still there and will be transmitted.  Also, as mentioned above, when you click on it to highlight/edit then it will again be visible.
 
I've asked Cakewalk about changing this so that longer messages/data will be shown but there are so few people that have this need that it isn't worth the time and effort to code it into Sonar (my summation, not Cakewalks).  It's actually quite strange because Sonar 8 and before would do this but once the "X" versions came out the above problem occurred.
 
I hope this answers your question.  The data is still there...just click on it to edit it.
 
Cheers...Shawn

Thanks Shawn - I will do it again and try what you suggest.
 
PS: I had given up on this getting any answer, so I appreciate you taking the time :-)