Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsFormsForms ProgrammingQueriesModules / DAO / VBAReports / PrintingMacrosDatabase DesignSecurityConversionImporting / LinkingSQL Server / ADPMultiuser / NetworkingReplicationSetup / ConfigurationDeveloper ToolkitsActiveX ControlsNew UsersGeneral 1General 2
Access DirectoryToolsTutorialsUser Groups
Related Topics
SQL ServerOther DB ProductsMS OfficeMore Topics ...

MS Access Forum / Modules / DAO / VBA / March 2008

Tip: Looking for answers? Try searching our database.

#NUM! in linked excel workbook

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
ragtopcaddy - 26 Mar 2008 16:32 GMT
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.

Signature

Bill Reed

"If you can't laugh at yourself, laugh at somebody else"

ragtopcaddy - 26 Mar 2008 18:32 GMT
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!

Signature

Bill Reed

"If you can't laugh at yourself, laugh at somebody else"

ragtopcaddy - 26 Mar 2008 18:33 GMT
Even CStr([Impact Description]) doesn't stop the #NUM!

Signature

Bill Reed

"If you can't laugh at yourself, laugh at somebody else"

Jeanette Cunningham - 26 Mar 2008 20:52 GMT
Bill
here is a link to a previous answer to this problem

   http://groups.google.com/group/microsoft.public.access.externaldata/browse_threa
d/thread/ea451c229b1e1a1a/41ee692ce83f361a?lnk=gst&q=%23Num#41ee692ce83f361a


Jeanette Cunningham

> Even CStr([Impact Description]) doesn't stop the #NUM!
ragtopcaddy - 27 Mar 2008 13:50 GMT
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
[quoted text clipped - 4 lines]
>
>> Even CStr([Impact Description]) doesn't stop the #NUM!

Signature

Bill Reed

"If you can't laugh at yourself, laugh at somebody else"

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.