Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 310 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
C/ODBC , Date Problem in SQL Server
ouredp
Member Posts: 56
Using Navision 3.7, CODBC 3.60 connecting to SQLServer,
we have problems in trying to export tabledata containing date format fields from Navision to SQL Server.
It seems that records containing 0D cause the error.
Insert Error, Column 120 "Order Date" , "DB_TYPE DBTIMESTAMP" Status6 Overflow
Does anybod know how to solve the problem ?
we have problems in trying to export tabledata containing date format fields from Navision to SQL Server.
It seems that records containing 0D cause the error.
Insert Error, Column 120 "Order Date" , "DB_TYPE DBTIMESTAMP" Status6 Overflow
Does anybod know how to solve the problem ?
0
Comments
Navision can handle dates from the year 0 up to 9999
SQL Server can handle dates from the year 1750 (standard) to an date which is set in the server properties.
Can you check your data?
Greetings,
...
Everybody on-line.
...
Looking good!
Finally we discovered that odbc creates the tables with smalldatetime formats.
After changing smalldatetime into datetime it works fine. Empty date fields are imported with 1753-01-01