I have a destination workbook tied to 12 source workbooks. The data being
pulled in from the source workbooks varies - some numbers, %'s, dates, and
text. Links are working great; but any lengthy text entries are cut off at
~253 characters.

I can get around this issue by opening the source file(s) that have the long
entries. When I do that, the complete text/fields appear in my destination
workbook. However, I'd like to get around this and not have to have all 12
source workbooks open to ensure I see complete fields.

I don't believe this is being limited by memory available as I've rebooted
to free up available memory, increased my paging file, etc. with no impact to
the number of characters that appear.

The destination and source workbooks are stored on the same SharePoint
network site. My links don't reference a named range...they define the
specific location/name/cell; so named range-related limits shouldn't be in
play. I'm running Excel 2003.

In case it matters, the source workbooks are also the destination of some
view-only information from the destination workbook - data is being shared
both directions.

That's the way excel and windows work. You're going to see 255 characters until
you open the sending workbook and recalc.

That's the only workaround that I know.

ScottFisher2004 wrote:

I have a destination workbook tied to 12 source workbooks. The data being
pulled in from the source workbooks varies - some numbers, %'s, dates, and
text. Links are working great; but any lengthy text entries are cut off at
~253 characters.

I can get around this issue by opening the source file(s) that have the long
entries. When I do that, the complete text/fields appear in my destination
workbook. However, I'd like to get around this and not have to have all 12
source workbooks open to ensure I see complete fields.

I don't believe this is being limited by memory available as I've rebooted
to free up available memory, increased my paging file, etc. with no impact to
the number of characters that appear.

The destination and source workbooks are stored on the same SharePoint
network site. My links don't reference a named range...they define the
specific location/name/cell; so named range-related limits shouldn't be in
play. I'm running Excel 2003.

In case it matters, the source workbooks are also the destination of some
view-only information from the destination workbook - data is being shared
both directions.

--

Dave Peterson

Hi Dave:
We have a program that exports phrases that need to be translated into
different languages into an excel spreadsheet. However, when the cell
exceeds the 255 characters, it is truncted. Isn't there a fix for this in
the registry HKey_local_machine\software\microsoft\jet\4.0\engi nes\excel\dword

if it is currently at 8, is the closer number to zero that allows more
characters/ i.e., less characters to be truncated?

Please advise.
thanki you,
Arlene

"Dave Peterson" wrote:

That's the way excel and windows work. You're going to see 255 characters until
you open the sending workbook and recalc.

That's the only workaround that I know.

ScottFisher2004 wrote:

I have a destination workbook tied to 12 source workbooks. The data being
pulled in from the source workbooks varies - some numbers, %'s, dates, and
text. Links are working great; but any lengthy text entries are cut off at
~253 characters.

I can get around this issue by opening the source file(s) that have the long
entries. When I do that, the complete text/fields appear in my destination
workbook. However, I'd like to get around this and not have to have all 12
source workbooks open to ensure I see complete fields.

I don't believe this is being limited by memory available as I've rebooted
to free up available memory, increased my paging file, etc. with no impact to
the number of characters that appear.

The destination and source workbooks are stored on the same SharePoint
network site. My links don't reference a named range...they define the
specific location/name/cell; so named range-related limits shouldn't be in
play. I'm running Excel 2003.

In case it matters, the source workbooks are also the destination of some
view-only information from the destination workbook - data is being shared
both directions.

--

Dave Peterson

I don't know.

Post back with your results after you test.

Remember to keep track of any changes you make to the registry so you can change
back if you need to.

ACarella wrote:

Hi Dave:
We have a program that exports phrases that need to be translated into
different languages into an excel spreadsheet. However, when the cell
exceeds the 255 characters, it is truncted. Isn't there a fix for this in
the registry HKey_local_machine\software\microsoft\jet\4.0\engi nes\excel\dword

if it is currently at 8, is the closer number to zero that allows more
characters/ i.e., less characters to be truncated?

Please advise.
thanki you,
Arlene

"Dave Peterson" wrote:

That's the way excel and windows work. You're going to see 255 characters until
you open the sending workbook and recalc.

That's the only workaround that I know.

ScottFisher2004 wrote:

I have a destination workbook tied to 12 source workbooks. The data being
pulled in from the source workbooks varies - some numbers, %'s, dates, and
text. Links are working great; but any lengthy text entries are cut off at
~253 characters.

I can get around this issue by opening the source file(s) that have the long
entries. When I do that, the complete text/fields appear in my destination
workbook. However, I'd like to get around this and not have to have all 12
source workbooks open to ensure I see complete fields.

I don't believe this is being limited by memory available as I've rebooted
to free up available memory, increased my paging file, etc. with no impact to
the number of characters that appear.

The destination and source workbooks are stored on the same SharePoint
network site. My links don't reference a named range...they define the
specific location/name/cell; so named range-related limits shouldn't be in
play. I'm running Excel 2003.

In case it matters, the source workbooks are also the destination of some
view-only information from the destination workbook - data is being shared
both directions.

--

Dave Peterson


--

Dave Peterson