Printing file with JPG vs. GIF

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I am trying to use the PrintDocument function to print my form that's loaded into memory.  I have always used this function, but apparently never with a JPG image on the form, only with GIF images.  This has always worked fine.

Earlier this year I switched from the COM to the DLL version.  Sometime after that I added a picture on the form that comes from a JPG.  I use the same AddImageFromFile to get the image in.  I still have GIF images in the file.  I did not have any problems.

I have had problems with the DLL throwing memory errors, so I decided to switch back to the COM.  I did not need to change code to do this.  However, now I get an error when trying to print.  The error is: 

Cannot create file "c:\windows\system32\inetsrv\7722.jpg". Access is denied

The name in the error is not the same as the name of the original JPG file.  When I switch to a GIF I don't get the error.  So it seems like the JPG gets added, but during the printing process the library must write the image itself out to a temp folder.

I'm using ASP.NET with IIS, so when I give the NETWORK SERVICE user full permissions to the inetsrv folder, I do not get the error.  But that's not a realistic solution for my published application.

I am using the old iSED version of the library, version 4.42.  I had switched to the DLL version 7, but in order to go back to the COM version I needed to back to the last validated version.  So if this is a known problem that's fixed in version 7, I'm not sure what I would do.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Jim Sullivan Members Profile Find Members Posts Team Player Joined: 10 Nov 05 Location: United States Status: Offline Points: 36	Post Options Post Reply Quote Jim Sullivan Report Post Thanks(0) Quote Reply Topic: Printing file with JPG vs. GIF Posted: 15 Oct 09 at 6:12PM
	I am trying to use the PrintDocument function to print my form that's loaded into memory. I have always used this function, but apparently never with a JPG image on the form, only with GIF images. This has always worked fine. Earlier this year I switched from the COM to the DLL version. Sometime after that I added a picture on the form that comes from a JPG. I use the same AddImageFromFile to get the image in. I still have GIF images in the file. I did not have any problems. I have had problems with the DLL throwing memory errors, so I decided to switch back to the COM. I did not need to change code to do this. However, now I get an error when trying to print. The error is: Cannot create file "c:\windows\system32\inetsrv\7722.jpg". Access is denied The name in the error is not the same as the name of the original JPG file. When I switch to a GIF I don't get the error. So it seems like the JPG gets added, but during the printing process the library must write the image itself out to a temp folder. I'm using ASP.NET with IIS, so when I give the NETWORK SERVICE user full permissions to the inetsrv folder, I do not get the error. But that's not a realistic solution for my published application. I am using the old iSED version of the library, version 4.42. I had switched to the DLL version 7, but in order to go back to the COM version I needed to back to the last validated version. So if this is a known problem that's fixed in version 7, I'm not sure what I would do.

Ingo Members Profile Find Members Posts Moderator Group Joined: 29 Oct 05 Status: Offline Points: 3530	Post Options Post Reply Quote Ingo Report Post Thanks(0) Quote Reply Posted: 15 Oct 09 at 8:37PM
	Hi Jim! These working files (ipg) you described were in the iSED-version - not in "our" later version and i think not in the newer 7.* versions? Cheers, Ingo

Jim Sullivan Members Profile Find Members Posts Team Player Joined: 10 Nov 05 Location: United States Status: Offline Points: 36	Post Options Post Reply Quote Jim Sullivan Report Post Thanks(0) Quote Reply Posted: 16 Oct 09 at 3:00AM
	OK. As I said, I had to go with the iSED versions based on validation and timing. I can try the newer version to see if it's fixed there. Thanks.