Prev: problem emailing attachment with COD method
Next: Loading Excel via VB - Resize issue with over 255 characters in a
From: Dee Earley on 9 Jul 2010 09:36 On 09/07/2010 14:03, Mayayana wrote: > Or to put it another way, if they're making good > money on their particular soup recipe there's no > reason they should be interested in techniques for > customizing their stove. :) Nice analogy :) Personally, I don't work on soup, but stick to bangers and mash :p (Again, using whatever stove I'm given) -- Dee Earley (dee.earley(a)icode.co.uk) i-Catcher Development Team iCode Systems (Replies direct to my email address will be ignored. Please reply to the group.)
From: Mayayana on 9 Jul 2010 10:16 | | Personally, I don't work on soup, but stick to bangers and mash :p That sounds like it's probably more profitable than soup. If you could offer an English language version you might even find bigger market.... (He says while ducking behind a rock for cover. :)
From: Dee Earley on 9 Jul 2010 11:07 On 09/07/2010 15:16, Mayayana wrote: > | > | Personally, I don't work on soup, but stick to bangers and mash :p > > That sounds like it's probably more profitable > than soup. If you could offer an English language > version you might even find bigger market.... > > (He says while ducking behind a rock for cover. :) Bangers and mash is about as British as you can get!!! Heathen :p -- Dee Earley (dee.earley(a)icode.co.uk) i-Catcher Development Team iCode Systems (Replies direct to my email address will be ignored. Please reply to the group.)
From: Tom Shelton on 9 Jul 2010 12:20 Mayayana wrote on 7/9/2010 : >> No one apparently wants to learn COM/OLE. <g> >> But it is absolutely necessary to move from an intermediate to >> 'advanced' Windows programmer. >> > > I'm often surprised by that lack of interest. It probably has to do with the fact that most developers have moved on to .NET (where COM still exists but is increasingly unimportant), Java, Ruby, Python, etc, etc. All languages, that in the main don't care about COM. All can interact with it if needed - but, it's generally not needed for day to day work. I used to care a lot about COM when I was doing VB.CLASSIC... Now, not so much. -- Tom Shelton
From: Karl E. Peterson on 9 Jul 2010 12:40
Paul Clement expressed precisely : > On Thu, 08 Jul 2010 14:58:01 -0700, Karl E. Peterson <karl(a)exmvps.org> wrote: > > � >> . I did not find any CLSIDs that referenced msado15.dll directly. > � > > � > That's puzzling because ADO is part of WIndows OS since 2000. > � > > � >> My > � >> understanding is that the interfaces are registered through the ADO > version � >> specific type libraries. > � > > � > When you look at the ADO references there are multiple references > � > available as I'm sure you've noticed. All but the most recent > � > reference are TLBs. The most recent is to the msado15.dll. > � > � You gotta remember, Paul's just here as an Agent of FUD. > > Believe it or not, I'm a double-agent working for KAOS. I *knew* it! ;-P -- ..NET: It's About Trust! http://vfred.mvps.org |