I read your post and understand your concerns comp
Post# of 30028
I tried to put myself in Gerald's shoes a few weeks before Copenhagen. He knew he had promised the complete LymPro data at the Conferences, but for whatever reason the testing got delayed. It WASN'T obvious at that point if the testing would be complete by the #C4CT Conference but he made a decision to move forward... trusting that the testing WOULD get done. It didn't. Ouch!
He made a judgement call, and it didn't work out. I've done that before. Has anyone else? He didn't want to slow down the pps momentum we were gaining as we entered July. If instead he had played it conservative and announced three weeks before Copenhagen that none of the data would be completely finished for either Conference, our pps momentum would have been killed! He had a tough decision to make. Hindsight is always 20/20.
We may question how he handled the communication during July, but I truly do not believe it was a question of character. He was trying to do what was best for the stock price and the shareholders. He took a chance it would get done, and it backfired on him, big time!
But the data, by the way, was very well received by scientists and the Pharma people attending the Conferences. (Key Opinion Leaders; KOLs) And from the blog and his other comments this past week all of the catalysts and milestones are on track for the remainder of the year. He is basically saying we will get a LymPro partner in September. Dandy was wondering if this partner would have a pedigree and pay big up front money. Well, by the sound of yesterday's blog, the stock value MIGHT even have a chance of getting to $2.00 dollars before we up list. (Not a promise) Needless to say he is pretty confident about how the catalysts are going to increase shareholder value, the LymPro partner being the biggest one.
I think these kind of things happen with a small biotech trying to make it big. There are risks involved, but that's why we'll get the big returns when it does take off. It's called: RISK RETURN. But you know that:-)