Environment versions
Network:
Windows 2003 Server
Hi Al,
"EXTERNAL" seems to tell the project manager "don't miss pulling in this piece", in this case a procedure. I looked at that one. But I tried it anyhow (took out my fake function and put EXTERNAL PROCEDURE EnablePrinter) and the PM still complains.
I know with a library file (e.g. foxtools.fll) I hook them in via "Code, API Libraries" and then I "exclude" them and then I think the PM recognizes the functions within the api file. But how would I hook in an activex object like "cdintfex.dll" in the same way (I tried inserting it but then I got a different error).
Any other thoughts?
Albert
>>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.
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only