by mga » Mon Oct 30, 2006 7:09 pm
why would i want to detect if the pdf module is available? ordinarily i wouldnt but in this case, i construct the document file name based on what i can tell about the users environment and the file name determines which type of file gets written. so, if i just assume that the pdf module is available and correctly installed and i do a WriteDoc("mypdf.pdf") then i end up with a file called mypdf.pdf written to disk even if the pdf module is not there. WriteDoc() does tell me that the write failed but i still have to clean up the unwanted, empty pdf file. i can do that. its no big deal but i would rather not have to do that. maybe the left over file is a consequence of WriteDoc() trying to clean up after itself and not being able to for some reason. whether there is a bug in WriteDoc() or whether the problem only occurs if i run VPE from the Progress 4GL doesnt matter to me because if i can find out if the pdf module is available before constructing the filename then i can avoid this problem.