Quirks with 2000???

[SE Freight Lines]

We have been using the PDF Converter utilizing the cdintf.dll commands in an Active X format on an NT machine for a while now with no major issues. We are trying to move the functionality to a 2000 machine with little success.

We search a directory for .htm files, rename them to .html, navigate the file in a webbrowser object, set the settings for the converter, and print to the printer. We then wait for completion prior to finding the next .htm file to convert. Like I said, this works on NT.

When we try this on 2000, the convertor does not 'engage' for all documents sent to it. It does not even create the .pdf file. Then maybe after 2 'skips', it creates the name of the current .html file as .pdf, but it turns out to actually be the original file sent.

Is this Security related? We have the same security settings on both PC's. Is it actually taking that long for the converter to engage? Help please.

Ex. Navigate ------------------ test1.html
Print to converter -------- (No file created)
Sleep 15 seconds for converter to convert
Navigate ------------------- test2.html
Print to converter -------- (No file created)
Sleep 15 seconds for converter to convert
Navigate ------------------- test3.html
Print to converter -------- (test3.pdf created)
Sleep 15 seconds for converter to convert

TEST3.pdf is actually the data from the initial TEST1.html.

Could 2000 be dealing with the sleep command differently than NT??
HELP!

Thanks-
John Germani
Southeastern Freight Lines

[Phil Davidson]

Here's a blind guess as to something that may help: Try GdiFlush() in your sequence of operations that print to the PDF converter.