I have a report on OBIEE, the date field I made it Custom format to MM-DD-YYYY I have also try [FMT:dateShort]. Once I exported to .csv I am Linking the file with MS Access 2007 and the date field I get an error #NUM! why is that ?
相关问题
- System.Data.OracleClient not working with 64 bit O
- Importing data from MS Access db to PostgreSQL db
- DoCmd.TransferSpreadsheet is not recognizing works
- Is there a way to apply theme on converted access
- How to programmatically convert Access 1997 .mdb t
相关文章
- COALESCE, IFNULL, or NZ() function that can be use
- CurrentDb.RecordsAffected returns 0. Why?
- How to embed ms-access forms in C# module?
- Sleep Lib “kernel32” gives 64-bit systems error
- increment function in plsql
- How to destroy an object
- Current version of data in database has changed si
- Close all VBE windows (MS Access, VB for Aplicatio
Either one of these could be the problem/solution:
The #Num! in Access is telling you the cell contains a mix of data; some digitit, some text, for example: 34G (or your '-') would throw a #Num!
You need to go back to the Excel and change the format of any cell containing both numbers and text to "mixed data" then save that sheet before importing to Access.
You can do this with a Macro:
Simply highlight cells needing the formatting, run the above macro, then re-save spreadsheet.
Or:
The #Num! error value means that the value in the field is too large (either positively or negatively) to be stored in the field, based on the field's DataType or FieldSize property setting. (https://support.microsoft.com/en-us/kb/209132)
Based on your format of the dates, I would try the first fix before anything else. Date =/= Number