I can not recommend this way of storing reports.
It gives you many problems with the end user/customer. Latest when he want to change the report.
Do it the "old fashioned" way. Create a separate file with the report.
If you want, create a basic report, convert it to a resource and add it. If somebody deletes the report file it will be rebuild from the compiled resource.
If you have a multi user application, store the report file in a database and read the file from the database. It makes more work, because not all options are in the property register and must be manual coded. But it gives you more flexibility and more freedom with you users/customers.