Same spreadsheet displays different column widths on different computers.
I have a spreadsheet that needs to be saved as a .PRN file, which makes the column widths critical as that determines how many spaces are between columns of the .PRN file.
When I open this file on one computer it says Column A column width = 17.
When I open this file on another computer it says Column A column width = 16.9.
Both computers are running Windows 7 and Excel 2010.
The spreadsheet has data in 9 columns (A:H) and each column has a slightly different width.
This column width difference changes the .PRN file by 2 Space characters. This causes problems to another program that reads this .PRN file because the field columns are in different positions than expected.
Both Excel 2010's are using the same default 'Body Font' and Font Size 11. The 'Office' Theme is common to both using Cambria & Calibri.
What setting or configuration is causing the one Excel Column widths to be different?
When I open this file on one computer it says Column A column width = 17.
When I open this file on another computer it says Column A column width = 16.9.
Both computers are running Windows 7 and Excel 2010.
The spreadsheet has data in 9 columns (A:H) and each column has a slightly different width.
This column width difference changes the .PRN file by 2 Space characters. This causes problems to another program that reads this .PRN file because the field columns are in different positions than expected.
Both Excel 2010's are using the same default 'Body Font' and Font Size 11. The 'Office' Theme is common to both using Cambria & Calibri.
What setting or configuration is causing the one Excel Column widths to be different?
Do you have any workbook file in the start up folder?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Another thought would be the default printer. Do they both have the same default printer assigned?
mlmcc
mlmcc
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Glad to hear you found the culprit!
ASKER
'Echo_S' pointed me in the right direction, but 'Resolution' was not the problem.
The actual solution was 'Text' size differences, which I documented in my comment for clarification.
The actual solution was 'Text' size differences, which I documented in my comment for clarification.