--- In [email protected], "Sheri" <sheri...@...> 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"
Public Function Search(Optional ByVal For As Variant, Optional ByVal WholeWord
As Variant, Optional ByVal CaseSensitive As Variant, Optional ByVal
ReplacingWith As Variant) As Objects 'Look for occurrences of text that matches
specific criteria / Return value: The found or replaced text / For: What to
look for as String / WholeWord: If true, then disregard text embedded within a
larger word as Boolean / CaseSensitive: If true, then search only for text that
matches case as Boolean / ReplacingWith: What to replace the found text with,
either a string or a special character as String
Same Search function as it currently appears within return from
appRef.get_object_documentation("fpth")
function: Objects* Search(VARIANT for, VARIANT wholeWord, VARIANT
caseSensitive, VARIANT replacingWith); Look for occurrences of text that
matches specific criteria / Return value: The found or replaced text / For:
What to look for as String / WholeWord: If true, then disregard text embedded
within a larger word as Boolean / CaseSensitive: If true, then search only for
text that matches case as Boolean / ReplacingWith: What to replace the found
text with, either a string or a special character as String;
Regards,
Sheri
