--- In [email protected], "entropyreduction" <alancampbelllists+ya...@...> wrote: > > --- In [email protected], "Sheri" <sherip99@> wrote: > > > > --- In [email protected], "entropyreduction" > > <alancampbelllists+yahoo@> wrote: > > > > > Yeah, that makes sense. Remember, I do two passes. You see error > > > message for second pass. Pass I: Guess. Pass II: send everything > > > in as strings (logical order: I keep track of whether any > > > parameter was converted by guess in pass one: if no such > > > conversion made, no point in Pass II).
I think the only reason you are making Pass II with all strings was an effort to remove the com exception failure of my Search method. Reviewing old messages, the old com exception was not the one for Type Mismatch, it was for Invoke Failed (which would now be replaced with the app error message). Is the error sys code 80020005: "Type mismatch" the same as DISP_E_TYPEMISMATCH? Maybe for version .72, it would be enough to remove Pass II. Lets see if there are any Type Mismatch errors. If not, the only niggling issue would be faulty skipped parameters. If nothing more can be tried there, could just document it. When ready to tackle a new version, can possibly enable arrays and events. Regards, Sheri
