See, in COM there are no error descriptions, ONLY a numeric error code (the
so called HRESULT).
You have to analyze this code.
--
Regards
Thomas Tomiczek
THONA Consulting Ltd.
(Microsoft MVP C#/.NET)
--
Still writing SQL and dealing with DataSets?
Why dont you use our EntityBroker - the most advanced o/r and business
object toolkit in town.
"Christoph Seidel" <chris66...@gmx.de> wrote in message
news:ap0vaa$qraq2$1...@ID-143718.news.dfncis.de...
yeah, of course, but the errorcode always *changes* for the *same*
operation, really weird!
same line of code, same parameters
well, as i said: weird!
--
Regards
Thomas Tomiczek
THONA Consulting Ltd.
(Microsoft MVP C#/.NET)
--
Still writing SQL and dealing with DataSets?
Why dont you use our EntityBroker - the most advanced o/r and business
object toolkit in town.
"Christoph Seidel" <chris66...@gmx.de> wrote in message
news:ap11l5$qcrgq$1...@ID-143718.news.dfncis.de...
(a) can it be that one of the parameters is a pointer and shows to random
data, thus creating different errors?
(b) can it be that the component is depending on external state?
Give details :-)
--
Regards
Thomas Tomiczek
THONA Consulting Ltd.
(Microsoft MVP C#/.NET)
--
Still writing SQL and dealing with DataSets?
Why dont you use our EntityBroker - the most advanced o/r and business
object toolkit in town.
"Christoph Seidel" <chris66...@gmx.de> wrote in message
news:ap151d$ql2ml$1...@ID-143718.news.dfncis.de...
LOL, i was waiting for this question :)
ok, eat this:
//items is type of Outlook.Items
//filter is a where-clause which contains a field which is not part of the
folders property collection, thus an exception is thrown
it is always the same empty folder, thus always the same items collection
(zero members) and always the same filter
try {
hits = items.Restrict(filter);
}
catch(System.Runtime.InteropServices.COMException e) {
if (!e.Message.StartsWith("The property")) throw e; //TODO: bullshit
workaround for mutating e.ErrorCode
}
Have you tried asking around in the Outlook newsgroups? Just to see whether
this is an error with the object model, or with the interop layer?
--
Regards
Thomas Tomiczek
THONA Consulting Ltd.
(Microsoft MVP C#/.NET)
--
Still writing SQL and dealing with DataSets?
Why dont you use our EntityBroker - the most advanced o/r and business
object toolkit in town.
"Christoph Seidel" <chris66...@gmx.de> wrote in message
news:ap1mn3$qaada$1...@ID-143718.news.dfncis.de...
damned, you are right, it's an OL bug (feature?)
Just a a suggestion for interop- try to leave the .NET groups as fast as
possible. When you are sure that the interop part works, the gsupport areas
for the products you basically interop WITH area a way better area to get
help. Like finding a workaround for this thing here.
--
Regards
Thomas Tomiczek
THONA Consulting Ltd.
(Microsoft MVP C#/.NET)
--
Still writing SQL and dealing with DataSets?
Why dont you use our EntityBroker - the most advanced o/r and business
object toolkit in town.
"Christoph Seidel" <chris66...@gmx.de> wrote in message
news:ap334b$qjnt3$1...@ID-143718.news.dfncis.de...