Generate the report, then bring your mouse cursor up to the Header
row. (In your screenshot where it says Acco...|2...) Position the
cursor at the column divider ( | ).
The cursor should change to a double facing arrow. At that point
drag the divider to the right so as to increase the column
HTH -Kevin N.
To be honest, I've not seen this happen before, when first opening
a report. It should not happen again as I believe that column
widths are now 'remembered' from their last setting.
Glad to hear that it's working now.
8 Posted by William Schwartz on 13 Feb, 2012 11:44 AM
For me, then column widths are not remembered. Each time, the reports open completely unreadable until I manually adjust all the column widths. Perhaps in memorized reports they are remembered, but not in regular reports as far as I can tell. To me this seems like a bug, although a new one here, as it did not used to happen.
I’ve already tried rebooting the Mac, which did not solve it.
Does this phenomenon present itself in all reports or only with the
I & E report?
Does MD have any problem 'remembering' other settings? For
instance, the settings in 'Preferences'. If so, it might indicate a
write permissions issue.
I see that in your OP you've provided your MD version and OS.
So as to assist the Moneydance support staff in sorting this out,
also provide the version of Java that you are running.
To do so, go to: Menu bar > Help > Console Window: Copy and
Past the first four lines of text into your next post so that all
of the pertinent information is provided as a whole.
HTH -Kevin N.
Support Staff12 Posted by Jon Hoover on 16 Feb, 2012 09:27 PM
First I want to say thanks to James and Kevin for the A+
William, that is a very unusual bug, especially since it is not
remembering the changes you are making.
Could you open up the console window and send in any errors that
may come up while you open the I&E report?
Jon Hoover, Moneydance Support
Ok, let's try this from another angle. Could you please create a
new, blank Moneydance data file, enter a few dummy transactions,
then run an I&E report and see if the issue recurs? This will
help us to see if the issue is specific to your data file, or to
your system. Let me know and we'll go from there.