After installing Cap 5 patch 5.0.2.630 can not insert a text animation

Question

I installed the 5.0 patch yesterday and today I cannot insert a text animation in my project. I have tried both Insert > Text Animation and Shift+Ctrl+X and nothing happens in either case. I seem to be able to insert everything else (at least the appropriate dialog boxes display). I was apprehensive about an upgrade during a project but did it because I hoped it would resolve some of the audio issues I am seeing.
I do have a couple of text animations that were working fine since I started the project several months ago, now they work but in a halting sort of way. I thought maybe they had become corrupted and was going to delete and re-insert them but Captivate won't let me now that I have patched it.
I have seen a number of people indicate that they gave up on text animations because they are pretty unpredictable for the end user of the published project - anyone feel otherwise?

Answer 1

Following up regarding my bug report, in case this info is useful to others..
Adobe contacted me via phone and, after we spent a considerable amount of time troubleshooting, the rep determined that my project was corrupted. Since the problems began after the patch was applied, it seemed reasonable to think that it somehow precipitated the issues, but the rep did not feel that was an accurate conclusion. I was concerned that I had now lost a lot of work because, even when I opened older backed up versions of the project, I encountered the same issues. The rep explained that there would not be a lot of rework because I could, in small batches, copy slides from the corrupted project to a new project (except for the Quiz review slide, which I needed to allow Captivate to create automatically in the new project). I was glad to hear this but unfortunately discovered (and the rep did not seem to expect) that not all of the project features copied. Most significantly, Master pages,  Advanced Actions, and object names did not copy over. Those all had to be recreated and reconfigured on the appropriate slides. So there was quite a lot of rework after all.
Once the substantial rework was completed, I was still having numerous problems working in and running the published project (65 slides total, 3 FLVs). After digging through the forums some more, I decided to break up the project and try the Aggregator, which was a failure. The project would not run. Then I turned to the post about daisy-chaining (#3445696) and I have been able to get things working. I definitely wished I had tried the multi-project route much sooner, but hadn't seen any indication that 65 slides with 3 FLVs was too big of a project.
Regarding the daisy-chaining: I was unable to get the projects to work by following the instructions to (1) use separate published project folders (2) use relative links to call the next project (3) ensure the folder was a trusted location in my Flash settings. Following these guidelines, the project did work when running on my C drive, but when I copied it to our network, it always threw up an error that it couldn't find the daisy-chained projects. I got it to work by scrapping the use of daisy chaining through the Publish End setting, putting all files in one folder, using a button on the last slide of each project to call the next project, and for the button action, using only the file name (not the relative path) of the project to launch.
I hope some of this info can help someone else avoid frustration.