Re: About protected memory in COM(in-process)
Tony Johansson <johansson.andersson@telia.com> wrote:
But I mean that the COM dll is doing exactly the same thing whether
it's VB that is using it or
C# asp.net.
So the error can't be in the actual code I assume.
Of course it can be. The usage pattern is different, the environment is
different. The problem was likely there all along, but the way the DLL
was used, it just never manifested.
So do you agree with me that I find it very very hard to assume that
there could be any programming bugs
like index out of bounds or such things.
Well, of course, I have no reason to doubt you when you describe your
state of mind. If you say you find it hard to believe, I can only assume
that you indeed find it hard to believe, and proceed to try and convince
you that it is, in fact, quite possible.
We use Oracle OLE DB providerns to connect to the database.
For example we have a CDataSource object named DS which is part of
MFC. Which is used in this way
hr = DS.Open("OraOLEDB.Oracle", "IDTHU1", "CCR_DTH_USER","
P55534552"); and then we have a CSession object called Session that
is used in this way. hr = Sesssion.Open(DS);
We have noticed that sometimes will this DS.Open throw an exception
which cause protected memory
Why didn't you say all this from the beginning, rather than describing
your problem in vague and general terms? Now, I personally know very
little about Oracle or OLE DB - hopefully others more knowlegeable would
chime in. But at least know they have some details to work with.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925