468,133 Members | 1,184 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,133 developers. It's quick & easy.

Problems with BinaryWrite, IE and Adobe Reader 6.0

Hi,

I'm having some problems with the Reponse.BinaryWrite, IE 6.0 and Adobe Reader 6.0. When I try to write a pdf-file to an IE browser with a Adobe Reader 6.0 installed then it just displays a blank page and the earth on the top rigth corner keeps turning like it haven't read the pdf-file (for 10+ minutes on a lan).
If I change the settings on the Adobe Reader 6.0 to not open in a browser, then it works fine.
If I use Mozilla 1.4 then it opens fine as well.
It works fine as well with Adobe Reader 5.1.

The code looks like this:
[Some code that places the pdf-file in a byte array called vntStream]
Response.Clear
Response.ContentType = "Application/pdf"
Response.BinaryWrite = vntStream
Response.end

I have tried to place a Response.Flush after the BinaryWrite, but it just makes the Adobe plug-in say something like "document corupted".

Can anyone help, please.

/Jens
Jul 19 '05 #1
2 5051
Hi there,

Is this a typo:
Response.BinaryWrite = vntStream
BinaryWrite is a function, not a property. Have you tried persisting the PDF
to disk and Response.Redirecting?

Cheers,

Alan

"Jens S0nderby Munk" <js****@diku.dk> wrote in message
news:bg*********@munin.diku.dk... Hi,

I'm having some problems with the Reponse.BinaryWrite, IE 6.0 and Adobe Reader 6.0. When I try to write a pdf-file to an IE browser with a Adobe
Reader 6.0 installed then it just displays a blank page and the earth on the
top rigth corner keeps turning like it haven't read the pdf-file (for 10+
minutes on a lan).

If I change the settings on the Adobe Reader 6.0 to not open in a browser, then it works fine. If I use Mozilla 1.4 then it opens fine as well.
It works fine as well with Adobe Reader 5.1.

The code looks like this:
[Some code that places the pdf-file in a byte array called vntStream]
Response.Clear
Response.ContentType = "Application/pdf"
Response.BinaryWrite = vntStream
Response.end

I have tried to place a Response.Flush after the BinaryWrite, but it just makes the Adobe plug-in say something like "document corupted".
Can anyone help, please.

/Jens

Jul 19 '05 #2
"Alan" <SP******************@inspire.net.nz> writes:
Hi there,

Is this a typo:
Response.BinaryWrite = vntStream That is of course a typo
BinaryWrite is a function, not a property. Have you tried persisting the PDF
to disk and Response.Redirecting?

Yes, I have tried that, and it works, but this is not a option as the PDF-fiels are not public accessable and the access control is done by the application. The conplexity of the access control does not allow me to place the files in a tree structure with access control.

/Jens
Hi,

I'm having some problems with the Reponse.BinaryWrite, IE 6.0 and Adobe
Reader 6.0. When I try to write a pdf-file to an IE browser with a Adobe
Reader 6.0 installed then it just displays a blank page and the earth on the
top rigth corner keeps turning like it haven't read the pdf-file (for 10+
minutes on a lan).
If I change the settings on the Adobe Reader 6.0 to not open in a browser,
then it works fine.
If I use Mozilla 1.4 then it opens fine as well.
It works fine as well with Adobe Reader 5.1.

The code looks like this:
[Some code that places the pdf-file in a byte array called vntStream]
Response.Clear
Response.ContentType = "Application/pdf"
Response.BinaryWrite = vntStream
Response.end

I have tried to place a Response.Flush after the BinaryWrite, but it just
makes the Adobe plug-in say something like "document corupted".

Can anyone help, please.

/Jens




Jul 19 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

6 posts views Thread by Alec MacLean | last post: by
1 post views Thread by =?Utf-8?B?RGlja0o=?= | last post: by
2 posts views Thread by =?Utf-8?B?SmVycnkgQw==?= | last post: by
27 posts views Thread by didacticone | last post: by
1 post views Thread by gcdp | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.