--- In [email protected], "entropyreduction" <alancampbelllists+ya...@...> wrote: > > --- In [email protected], "Sheri" <sherip99@> wrote: > > > > --- In [email protected], "Sheri" <sherip99@> wrote: > > > > > > > > > Possibly this is just the unique way Adobe chose to do it, and I > > > was misled by the application's documentation? > > > > There is actually a descrepancy in parameter types as per the > > Parameter "type" and the help string for the previously discussed > > Search method. The application documentation presents the > > Parameter types from the help string instead of from the real > > Parameter Type. I think the reason they are variants in this case > > is because they are optional parameters. > > > > Following clipped from the vbaccelerator TLBHelp Browser window. > > > > Note the parameters are all "variants" yet in the help string > > they are "string" and "boolean". The application documentation > > shows the "Parameter Type" for those parameters as "String" and > > "Boolean" > > Yeah, they're saying in help what they expect the Variant to turn > out to be. Hopefully they will have done the Right Thing in their > code, so when e.g. the code for Search function runs, it will > take whatever comes in first parameter and coerce it to a BSTR, > whatever comes in as thirst param and coerce it to bool, etc. >
If that were the case, how would you explain the com exception errors I got previously when the search text happened to be all digits (unless I used the method_typed service instead)? I also recall errors setting properties in another service whose paramether needed the type to be a "double". Given 4.0, it gave a com exception. But given 4, it worked. Using method_typed, I could use 4.0. The property in question does not appear use variant, it has (per vbaccelerator TLBHelp's Browse tab) Public Property Let Version(RHS As Double) 'Version of the scripting environment Don't know what RHS means, but I don't see any "Variant" there. Regards, Sheri
