#NUM! in linked excel workbook

[ragtopcaddy via AccessMonster.com]

I'm getting all kinds of nonsense in this linked workbook. Text fields are
showing 0's for several rows, and #NUM! where there should be text. Other
text fields are showing text for several rows and #NUM! where there are 0's
in the linked excel spreadsheet.

The spreadsheet I'm linking to from Access, is itself a collection of pasted
links from another worksheet, which was copied from a sharepoint directory. I
can't link directly to the sharepoint file from Access2003.

 

[ragtopcaddy via AccessMonster.com]

One of the bizarre things that's happening is there is a field, [Impact
Description], that has several text entries in it that I can easily read in
my query. But if there is nothing in the field I get a #NUM!, which sometimes
aborts the query with a 'Number overflow' or something. #NUM! is supposed to
indicate that a number field can't display the data because it's not a number.
In this case, text displays properly, which indicates that Access doesn't
'think' it's a number field, but nulls appear as #NUM!. This is crazy!

 

[ragtopcaddy via AccessMonster.com]

Even CStr([Impact Description]) doesn't stop the #NUM!

 

[Jeanette Cunningham]

Bill
here is a link to a previous answer to this problem

http://groups.google.com/group/micr...e692ce83f361a?lnk=gst&q=#Num#41ee692ce83f361a

Jeanette Cunningham

 

[ragtopcaddy via AccessMonster.com]

Thanks Jeanette.

I will be sure to implement Jamie's solution on my laptop. The PC here at my
client site is another matter. I am awaiting a visit from IT.

Bill
here is a link to a previous answer to this problem

http://groups.google.com/group/micr...e692ce83f361a?lnk=gst&q=#Num#41ee692ce83f361a

Jeanette Cunningham

Even CStr([Impact Description]) doesn't stop the #NUM!