RE: [U2] Access to IBM knowledgebase for in-house developers

2006-11-12 Thread Brian Leach
Exactly ! A good knowledge flow opens people's eyes and creates opportunities. And it's not just an end user issue. Without knowledge flow where will the next generation of vars come from? Who will bring new blood and investment? How will we encourage developers into our market ? How much more

RE: [U2] Access to IBM knowledgebase for in-house developers

2006-11-12 Thread phil walker
Conspiracy Theory: Maybe IBM does not want a future MV environment, maybe they hope everyone will go to DB2...if so, then I hope it works. I think more likely they would go to Microsoft, where information is readily available. ;-) -Original Message- From: [EMAIL PROTECTED]

Re: [U2] Access to IBM knowledgebase for in-house developers

2006-11-12 Thread Ken Hall
As an IBM reseller of U2 products, I can assure you that your VAR or reseller can request that their users get access to the IBM documentation. You just need to ask the vendor who charges you for U2 support. Ken At 05:47 PM 11/10/2006, you wrote: Stevenson, Charles wrote: First, my own var,

RE: [U2] Access to IBM knowledgebase for in-house developers

2006-11-12 Thread Bill Haskett
Brian: I remember an speech years ago by an MV vendor proudly saying that 80% of his business was repeat business. He saw that as customer care. I saw it as lack of outreach. Who was right? For a few years, he; for the rest, you! Remember, in the long run we're all dead, so, it's no surprise

RE: [U2] Access to IBM knowledgebase for in-house developers

2006-11-12 Thread Debster
I don't know how 'aggressive' strategy 7 needed to be in oder to secure access to the knowledge base.. I took one phone call to them after I was booted from IBM because S7 held the license, and I was on in no time flat If a VAR is going to make excuses and deny access, its time to review when

RE: [U2] Access to IBM knowledgebase for in-house developers

2006-11-12 Thread Stevenson, Charles
I don't know how 'aggressive' strategy 7 needed to be in order to secure access to the knowledge base.. I meant that they were aggressive in getting the access mechanism for us in the first place. If I remember correctly, a couple years ago or so there was a nice announcement in the email