Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Are there any known problems with Acrobat 4?
Message
From
15/06/1999 14:58:17
 
General information
Forum:
Visual FoxPro
Category:
Third party products
Miscellaneous
Thread ID:
00230033
Message ID:
00230105
Views:
27
>>>>Last week, I posted a message describing a problem with using Adobe Acrobat 4 under Visual FoxPro 6, running on a Windows NT platform (Message Title was Outputting Reports in .PDF with Acrobat 4, thread #228100). Since then, several more of our customers have reported this problem of having the PDFWriter output to a PRINTER.TXT.PDF. It is becoming an urgent situation.
>>>>
>>>>Has anyone heard anything else from Microsoft, Adobe, or any other source, reporting this sort of problem and/or offering a solution or workaround for it? I'm approaching the end of my time limit to get this fixed, and I'm no closer to a solution now than I was a week ago.
>>>>
>>>>
>>>>Bill
>>>>
>>>>PS - While researching this problem, I visited the Adobe User-to-user forum. If I ever complain about the Universal Thread again, shoot me. This forum is a hundred times better than Adobe's!
>>>How do you assign file's name?
>>>Mark
>>
>>Mark,
>>
>>Filenames are created witht he following command:
>> lcFileName = oSession.cTempPath + SYS(3) + '.' + lcExtension
>>
>>oSession.cTempPath is a directory that is used for temporary files. It is usually C:\TEMP or some variant.
>>lcExtension is the file extension of the filename we are creating. If we do not put an extension on our filename, VFP will create the file with a .TXT extension. Since our printer is PDFWriter, the extension is PDF.
>>
>>Therefore, our filename lcFileName would be "c:\TEMP\12345678.PDF"
>>
>>As I mentioned, this has worked fine under Adobe Acrobat 3.
>>
>>Bill
>
>I believe this has to do with the FILETYPE if you set it to *.* then it will export without the TXT extension, BUT if you just change the extension on the filename it will export with the extension you added PLUS the default. I ran into this while exporting PS(EPS) (adobe postscript on NT) files, whereby it was exporting them with XXXX.PRN.EPS, I simply said not to use the print type, but rather all files type, and it dropped the prn extension.
>
>This might be some wacky Adobe thing.
>
>Keith
>
>PS: I had to mess with it manually to find out exactly what was happening.
>
>

Keith,

I'm a little fuzzy on where you're setting the filetype. Is this some sort of clause on the REPORT FORM command? Is it something that is set in the printer setup? I've never seen this clause before, and the VFP 6.0 help only refers to filetype in the Coverage Engine object.

Bill
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform