>Hi Y'all,
>
>In one of my procedure libraries, I create a PDF printer object from an ActiveX object and then do something like
>
>WITH loPDFWriter
>
>.EnablePrinter()
>.SetSIMPostScript()
>
>...etc
>
>Well the Project Manager complains that it cannot find "EnablePrinter" and any other methods called. I have got around the complaining by putting a "fake" function at the bottom of the procedure file e.g.
>
>PROCEDURE EnablePrinter
>PROCEDURE SetSimPostScript
>
>Is this the only way around this? Is there a command that would tell the PM that the method is available elsewhere?

Check out EXTERNAL PROCEDURE.