No. We support .DOCX and .XLSX files only which means that Office 2003 formats (.doc and .xls) are not supported. Note that we also do not support Word .dotx files and .xlsm (these are special Word/Excel templating files).
Our PDF generation is done using a 3rd-party component, and so we don't have any clear reason for why the file size is bigger. The only suggestion we can make is that any static embedded images in the template should be explicitly compressed. This can be done in Word by following the steps outlined at the link below:
Ultimately, every generation component is different in terms of how it converts the Word document contents. It's possible that our component will generate smaller files than the other programs given a different source Word/Excel file.
Currently we only support Microsoft Office tools - specifically Word and Excel. This applies to the XLSX and DOCX files uploaded as templates as well as any XLSX or DOCX files generated by the platform. Open Office and other such Office alternatives are not officially supported, though you may find these tools work in certain situations. However, any (likely) issues you encounter due to your use of a non-Office tool will not receive any support from us.
The issue is likely due to the docx template being used in your Word data template. Usually this means that your Word doc is linked under the hood to an inaccessible dotx file (usually located on your personal PC or on a network drive). Now this docx file is obviously not available to the eForms Mobile platform when it generates the file and naturally is not found when you open the Word output file on another machine. What you need to do is clear the dotx template of your Word file, which will let the Word file default to the standard "Normal" dotx template. Follow the steps below to clear the problem dotx template:
The issue is likely due to the placement of static images within repeatstart and repeatend tags in your Excel data template. In most cases, the images have not been located and formatted correctly within a cell or cell range. Follow the steps below to correct the placement of static images within your repeat sections:
There are several possible causes for this, but a common reason is you have specified a custom page area in your Excel template file which cuts off your generated contents. Our PDF renderer will obey your defined printable page area, excluding any content outside the defined page.
To diagnose this as the problem:
With repeating sections that contain images in your report output, it can be difficult to prevent images being cut over pages, mainly because the images could be landscape or portrait in orientation. This variability means it is difficult to predict the height of the incoming images. The best option is to ensure that the chosen cell height you assign to the image fields are a factor of the page height. E.g., ensure that, say, twice image cell height adds up to exactly the typical printed page height. This way, if you had 3 rows of images, then 2 rows would fit into the first page exactly and the 3rd row would go onto the next page without any image cut-off.