wrong field length (twice the size it should be)

[crystalvictim]

hi,
i've noticed some strange behaviour when using an access-db as a data source for my report. (i'm using CR8.5 professional)
if i connect with the database via ODBC or OLE, the field explorer shows all the textfields with twice the length they have in ms-access.
e.g., i have a field "name" which has been defined as character (length 50). in my report this field now appears as character (length 100).
when connecting to the access-db via "database file", everything's fine.
has anybody made similar experiences and/or knows if this is a bug and how it can be fixed? (i searched the knowledgebase but only came across c2003327 which describes such a behaviour, but they say it has been fixed since CR7.0 maintenance release 1). :-(

 

[Naith]

You haven't mentioned driver name and version you're using.

When you verify database, does this address the problem?

Naith

 

[crystalvictim]

I'm afraid no, it doesn't.
Also, we're not changing the field length in the database. This effect already appears when using connecting to the db for the first time.

 

[Naith]

You might consider applying the latest hotfix from Crystal Decisions support site.

I do recall using a hotfix solution to overcome Crystal reports truncating field lengths where those reports were using stored procedures. (e.g. VARCHAR2(100) becoming STRING(25) in Crystal.)

Naith

 

[crystalvictim]

hm.... no stored procedure at all in this report, but i'll keep this advice in mind and forward it to our crystal administrators ;-)
I thought about a buggy driver (OLE/ODBC) - would that be possible? I don't know how the access is done when using 'database file' but I guess it can't be done by using the same technique as ODBC/OLE as this produces the correct result.

 

[Naith]

It may well indeed be your drivers - in fact, it's not just possible, it's probable - which is why I asked you for the name and version of driver that you're using.

Naith

 

[crystalvictim]

ups, that must have slipped my attention - sorry!
well, ODBC uses the 'microsoft access driver' version 4.00.6019.00.
With OLE, we've been using 'Microsoft Jet 4.0 OLE DB Provider'.
But I have no idea what the 'database file' connection method uses :-(