[Oledb-dev] Provider question

[Arvo]

Hello Shachar,

>>Sorry to kick in :) I've deralt with siliar problems, compiling driver with VS.NET 2002. My workarounds and comments:
>>  
>>
> And you didn't say anything? How is free software supposed to improve if
> people keep their suggestions to themselves?

Very easy: I've no experience with ATL neither  OLEDB. I just tried make driver compile under VS.NET - I made two ugly hacks to achieve that, no more. I'd no idea, what such hacks do break, especially this ATL_CATEGORY thing. Seeing somewhat similar workarounds, made by another person, I can be sure that I was on the right way.

You're always talking about code quality, btw :)


>>   DBROWOFFSET cRowsInSet = (DBROWOFFSET)pT->m_rgRowData.GetCount();
>>
> MS? Changing interfaces like that? No way!

This is the "The one microsoft way" or how they call that themselves.

(code skipped)

>>Of course it would be correct include some VS version checking preprocessor #if.
> Except we depend on the ATL version, not the compiler version at all.

Well, my fault - of course this depends on ATL version (although for Visual Studio this doesn't matter so much - ATL and VS versions are tightly related).

> The current CVS should compile fine on VS2005, according to my
> understanding (I don't have it).

Will check out soon, thanks for corrections!

-- 
Best regards,
 Arvo                            mailto:arvox at hot.ee