In the past few weeks some of our users are experiencing issues when opening Powerpoint files that we are generating with .Slides. Some users that have Office 2003 installed are getting the warning "Office File Validation detected a problem while trying to open this file. Opening it may be dangerous". I was reading that Microsoft recently released updates for Office 2003 and 2007 which implemented Office File Validation. I would assume these users have had their Office 2003 updated with this.
The reason I am inquiring on this forum about this is that it is not occurring on all the Powerpoint files that we are generating with Aspose, just one in particular. Do you guys know of anything in Aspose.Slides in particular that may trigger this validation warning? I am comparing the code we use to generate the Powerpoint file that has the warning, versus files we generate that do not generate the warning and am not seeing anything drastically different between the two as far as functions or techniques we are using.
Any help or info on this would be appreciated. Thanks.
I have tried to understand the issue shared. It will be so nice of you if you may please share the source presentation, code snippet that is applied on presentation and resultant problematic output presentation with us, so that we may investigate and reproduce the same on our end. Please also share the version of PowerPoint 2003 that you are using and exhibiting the issue.
I included the original source presentation, the Powerpoint template, the code file and a partial output file. I was not able to include the total output file as the data in it was company proprietary. I scrubbed out the proprietary data. I hope that it is sufficient.
The code pulls info from a database and populates the powerpoint.
The version of Powerpoint I am using is Powerpoint 2003 (11.8335.8341) SP3.
We are sorry for your inconvenience. Can you please try using Aspose.Slides for .NET 6.4.0 on your end as some of related issues have been resolved in past releases. If there is still an issue then kindly share the scale down version of the code snippet that we can test on our end as the code snippet shared in your previous post involves calls to database and we unfortunately does not have the same database on our end. I am hopeful that issue will be resolved with new version but if there is some issue still, I will expedite things on my end to help you further. Please also share the problematic output presentation as well.