Zero Length String and Garbage

[Olly]

I have an Access 2007 database that is linked to tables stored in an
Interbase/Firebird (version 1.5) database. Any fields with zero
length strings in them are displayed as garbage (eg: "Â緪ꔒ䃣4 "). I do
not think the problem is with the ODBC driver, because other
applications that use the same driver do not show these problems.

Unfortunately, I cannot change the data in the linked table, because
it is generated by a third party application, and may cause problems
if I change any of the data stored in the linked table. Does anyone
have any ideas to how I can correct this problem, as it is getting
quite serious now.

cheers
Olly

 

[Jerry Whittle]

What happens when you put in the criteria of ="" in a query?

How about Len([TheFieldName]) in the field of a query?

 

[Olly]

Jerry

Searching by ="" returns 12 results, way less than the fields with
garbage in them.
Searching by len returns an integer grater than zero, but not
necessarily the same length of the string displayed. It is either
equal to or grater than the length of the string displayed.

cheers
Olly

What happens when you put in the criteria of ="" in a query?

How about Len([TheFieldName]) in the field of a query?
--
Jerry Whittle, Microsoft Access MVP
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.

I have an Access 2007 database that is linked to tables stored in an
Interbase/Firebird (version 1.5) database.  Any fields with zero
length strings in them are displayed as garbage (eg: "Â緪ꔒ䃣4 ").  I do
not think the problem is with the ODBC driver, because other
applications that use the same driver do not show these problems.

Unfortunately, I cannot change the data in the linked table, because
it is generated by a third party application, and may cause problems
if I change any of the data stored in the linked table.  Does anyone
have any ideas to how I can correct this problem, as it is getting
quite serious now.

cheers
Olly

 

[Olly]

Bump, any chance of getting a response?

cheers
Olly

Jerry

Searching by ="" returns 12 results, way less than the fields with
garbage in them.
Searching by len returns an integer grater than zero, but not
necessarily the same length of the string displayed.  It is either
equal to or grater than the length of the string displayed.

cheers
Olly

What happens when you put in the criteria of ="" in a query?

How about Len([TheFieldName]) in the field of a query?

 

[John W. Vinson]

Bump, any chance of getting a response?

It sounds to me like the ODBC driver for Interbase is defective. Have you
reported this symptom to whoever developed the driver?

I don't know what I - or any of the other volunteers here - can do, since I
don't have Interbase (or a whole lot of spare time, for that matter).

 

[Olly]

Thanks for your reply. But there is no issue with the ODBC driver,
because other applications use the same driver without seeing the
unexpected data. Which to me indicates a problem with Access itself.

cheers
Olly

 

[James A. Fortune]

Thanks for your reply.  But there is no issue with the ODBC driver,
because other applications use the same driver without seeing the
unexpected data.  Which to me indicates a problem with Access itself.

cheers
Olly

Maybe a workaround can filter out the garbage. Try something like:

IIf(Len(IIf(FieldName IS NULL, "", FieldName) = 0, "",
IIf(Asc(Left(FieldName, 1)) < 32 Or Asc(Left(FieldName, 1)) > 127, "",
FieldName))

James A. Fortune
(e-mail address removed)

 

[James A. Fortune]

Maybe a workaround can filter out the garbage.  Try something like:

IIf(Len(IIf(FieldName IS NULL, "", FieldName) = 0, "",

Try something more like something with a right parenthesis before the
'=' sign . Other parentheses might be needed or omitted.

James A. Fortune
(e-mail address removed)

 

[De Jager]

I have an Access 2007 database that is linked to tables stored in an
Interbase/Firebird (version 1.5) database. Any fields with zero
length strings in them are displayed as garbage (eg: "Â緪ꔒ䃣4 "). I do
not think the problem is with the ODBC driver, because other
applications that use the same driver do not show these problems.

Unfortunately, I cannot change the data in the linked table, because
it is generated by a third party application, and may cause problems
if I change any of the data stored in the linked table. Does anyone
have any ideas to how I can correct this problem, as it is getting
quite serious now.

cheers
Olly

 

[joelgeraldine]

km)====


ùklippjbçà"Olly" <[email protected]> a écrit dans le message de groupe
de discussion :
(e-mail address removed)...

 

[Guest]

It sounds to me like the ODBC driver for Interbase is defective. Have you
reported this symptom to whoever developed the driver?

I don't know what I - or any of the other volunteers here - can do, since
I
don't have Interbase (or a whole lot of spare time, for that matter).