Hi Peter
See if this is any better
Export["RequestedTable.xlsx", Join[{{"Header A", "Header B", "Header C", "Header D", "Header E", "Header F"}}, SetPrecision[Transpose@Table[{i}, {i, 7300, 7800, 100}], 5]]]
Paul.
At face value I can only assume that the results of your calculations don't have any decimal part, the results from your first example certainly don't, do you have a full example code I can try?
Strange, that's exactly how I want it to be...! The error messages occur, because the long Minimum-Function consists out of several minimum functions - and some of them will return errors if the requested number becomes too big and therefore cannot fulfill any constraint within them.
Anyways... I would love to know, why this is not working on my side. I also tried to increase the decimal part, but it will only show zeros... I wonder if this has anything to do with my Mathematica running on a Raspberry Pi or the Export itself being run on a Raspberry Pi, which does not run Excel by itself. Every time I have an exported file, I email it to a stationary PC and open it there. Shouldn't be a problem to my understanding, though?!
Good morning Paul,
Sorry for the late reply, I didn't have time to follow up with this during the last week...
Well, the calculations definately have a decimal part. They are shown in the intermediate results. The full code is attached. It'd be great if we can figure this out...!
BR, Peter
Hey guys,
is there nobody, who can help me out on this? Right now I'm thinking of a workaround to solve at least the precision-problem. I'll multiply the second value by 1000 or a Million and divide this after exporting in Excel. But that's probably not how it's ment to be, right?
P.S.: If you need the complete code of this Problem, please let me know.
