ADP report truncates field at 4000 characters

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

pfg_qa - 27 Oct 2005 19:23 GMT

Pardon the cross-post--I must have overlooked this NG when originally posting
to microsoft.public.access.reports. The below includes my original post as
well as some new findings. Original problem still exists.
X.
***************************
As the data comes into the report, I tried Debug.Print as well as writing the
text beyond the 4000 character mark to a textfile. It's just a bunch of
garbage.

Then I changed the datatype for the field in question from varchar(8000) to
text. This worked. It's a viable workaround, though I'd still be interested
in anyone else's ideas.

Thanks.
X.

"pfg_qa" wrote:

> Access 2000 (SP3) ADP report fronting SQL Server 2000 (SP3). Report uses a
> View as record source. Among the fields in the view is one defined as
> varchar(8000). Report works fine except it truncates the data in this one
> field at 4000 characters. Field is set to Can Grow. It continues to next
> page all right. Double-checked view in Query Analyzer--no problems there.
>
> What's odd is that it appears the data is returned to the report OK. When I
> check the length of the data in the questionable field during the
> Detail_Print event, it gives me the expected value. However, the report
> displays only the first 4000 characters.
>
> Tried using a stored proc as record source--same result. Tried a report
> with ONLY the field in question on it--same result. An unbound form in same
> app populated via an ADO recordset built via stored proc displays all data
> correctly.
>
> Any help is greatly appreciated.
> X.

Reply to this Message

Robert Morley - 27 Oct 2005 21:33 GMT

I don't know anything specific, but it sounds like some kind of bug where
the ADP is trying to interpret your varchar(8000) as an nvarchar(4000).

Since you've said that the text datatype works, if you want to keep your
varchar(8000), how about building an SP that uses the text datatype
externally, but converts it to a varchar(8000) internally?

Just a thought,
Rob

> Pardon the cross-post--I must have overlooked this NG when originally
> posting
[quoted text clipped - 44 lines]
>> Any help is greatly appreciated.
>> X.

Reply to this Message

pfg_qa - 27 Oct 2005 21:53 GMT

Yep--I ended up with a similar solution--converting the varchar(8000) to text
datatype in the views that act as report recordsources. This works just fine.

We're about to move to Access 2003. I'll be curious to see if I can
recreate the problem. I'll look into submitting it officially as an issue if
I can.

Thanks for your time.
X.

> I don't know anything specific, but it sounds like some kind of bug where
> the ADP is trying to interpret your varchar(8000) as an nvarchar(4000).
[quoted text clipped - 54 lines]
> >> Any help is greatly appreciated.
> >> X.

Reply to this Message

pfg_qa - 28 Oct 2005 14:37 GMT

I confirmed, at least on our test machines here, that this is NOT an issue
with Access 2003.
X.

> Yep--I ended up with a similar solution--converting the varchar(8000) to text
> datatype in the views that act as report recordsources. This works just fine.
[quoted text clipped - 64 lines]
> > >> Any help is greatly appreciated.
> > >> X.

Reply to this Message