Report Designer .bak file
Report Designer .bak file
Can anyone explain me the purpose of .bak file of report file. When we are doing changes it seems sometimes changes are saved to .bak file. http://forum.stimulsoft.com/posting.php?mode=post&f=8#
Re: Report Designer .bak file
Hello,
Can you please describe your issue in more details.
Thank you.
Can you please describe your issue in more details.
Thank you.
Re: Report Designer .bak file
Hi Aleksey,
I am developing my reports using sitecore stimulsoft report designer version 2009.3.600. Sometimes while I am working the changes I made are not saved no matter how many times I click the save button. When this happened I found that by deleting .bak file the changes could be saved again to the .mrt file. When it is saved a new .bak file is created in place of the deleted one. After that the changes would be saved normally and again after sometime the issue would occur.
Thanks
I am developing my reports using sitecore stimulsoft report designer version 2009.3.600. Sometimes while I am working the changes I made are not saved no matter how many times I click the save button. When this happened I found that by deleting .bak file the changes could be saved again to the .mrt file. When it is saved a new .bak file is created in place of the deleted one. After that the changes would be saved normally and again after sometime the issue would occur.
Thanks
Re: Report Designer .bak file
Hello.
I am sorry if my reply was crude.
However, I would like to clarify our position. According to our support policy the customers of our customers are not our customers.
For example, a company purchases our product to integrate into the application. Then the company sells their application to a customer. The customer finds a problem. He/she sends a bug report to the manufacturer who is our customer. If the issue is related with our product the manufacturer who is our customer sends the report to us. We fix it. Why we follow such rules of tech support? Because we do not know how the customer uses our product in their application.
Thank you.
I am sorry if my reply was crude.
However, I would like to clarify our position. According to our support policy the customers of our customers are not our customers.
For example, a company purchases our product to integrate into the application. Then the company sells their application to a customer. The customer finds a problem. He/she sends a bug report to the manufacturer who is our customer. If the issue is related with our product the manufacturer who is our customer sends the report to us. We fix it. Why we follow such rules of tech support? Because we do not know how the customer uses our product in their application.
Thank you.