In my understanding,
the COM object is a layer/interface between the caller and the object. All
Witango can do is call the exposed interface connections. I see no way for
Witango to arbitrarily mix these up. This is got to be a mix up with the
developer that created the COM interface.
For fun try calling
the wrong one, maybe this could be a work around till the COM interface is
fixed by the developer
-----Original
Message-----
From:
John Shaw
[mailto:[EMAIL PROTECTED]
Sent: Monday, October 27, 2003 1:38
PM
To:
[EMAIL PROTECTED]
Subject: Witango-Talk: COM
Problem
First, I had a meeting with a
programmer from ASI Consulting. I told him I was using Witango and
explained that it used to be called Tango. So he says, "I used to work
for a company in Toronto that had a product called Tango. Does anyone
remember Steven Moseley? I guess he was there very early in Tango
development.
Anyway, we were trying to get a
dll wrapper to work in Witango and the parameters were seemingly getting mixed
up. Steven ran a trace on SQL server and it showed that the item code
parameter had the quantity parameter value. Has anyone seen Witango
mix up parameters like that?
I hate this sort of thing because
there are so many programs involved: Witango, the dll wrapper, the wrapped
dll.
