S
ScottFisher2004
I was migrated from SharePoint 2.0 to 3.0 last week. On 2.0, I had numerous
'update' Excel files where people would submit information. Those files all
linked with a 'master' Excel file that consolidated all the information from
which I ran reports, etc. As some field entries in the 'submit' are large, I
had to have the submit files open when looking at the 'master' or those
fields would be cut off. This is due to an Excel limit...only shows ~255
characters per linked field unless the source file is open (pulled into
memory). Now that I've been migrated to SharePoint 3.0, the Excel workaround
no longer works. If I save the files locally, the Excel workaround works.
Given this occured with the migration to 3.0 AND the Excel functionality
works when the files are opened locally, I'm guessing that SharePoint 3.0
must do something differenty than 2.0 when opening a file (e.g., something
around the way (or where) it loads the file to memory) which is affecting
Excel functionality. Do you know of anything I can do in Excel to fix this
problem? Any thoughts on workarounds (other than saving all the files
locally every time I need to run reports)? FYI - I've submitted a post to
the SharePoint Server discussion board to see if they have any thoughts too.
Thank you for any thoughts/suggestions!!!
'update' Excel files where people would submit information. Those files all
linked with a 'master' Excel file that consolidated all the information from
which I ran reports, etc. As some field entries in the 'submit' are large, I
had to have the submit files open when looking at the 'master' or those
fields would be cut off. This is due to an Excel limit...only shows ~255
characters per linked field unless the source file is open (pulled into
memory). Now that I've been migrated to SharePoint 3.0, the Excel workaround
no longer works. If I save the files locally, the Excel workaround works.
Given this occured with the migration to 3.0 AND the Excel functionality
works when the files are opened locally, I'm guessing that SharePoint 3.0
must do something differenty than 2.0 when opening a file (e.g., something
around the way (or where) it loads the file to memory) which is affecting
Excel functionality. Do you know of anything I can do in Excel to fix this
problem? Any thoughts on workarounds (other than saving all the files
locally every time I need to run reports)? FYI - I've submitted a post to
the SharePoint Server discussion board to see if they have any thoughts too.
Thank you for any thoughts/suggestions!!!