Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Data type not compatible with the SQL Server data type
Votuc
Member Posts: 206
When I try to open the RTC, I get the following error:
The Purchase Header table contains a Microsoft Dynamics NAV Classic field data type that is not compatible with the SQL Server data type: Field: Name Type: Text50 SQL type: VARCHAR(60)
Page VEC Sales "Activities" must close.
I did a search and I did find some people with this error - but they were running NAV 3.70 and just told to upgrade to NAV 4. This is NAV 2009 SP1. Is there a way I can get around this?
The Purchase Header table contains a Microsoft Dynamics NAV Classic field data type that is not compatible with the SQL Server data type: Field: Name Type: Text50 SQL type: VARCHAR(60)
Page VEC Sales "Activities" must close.
I did a search and I did find some people with this error - but they were running NAV 3.70 and just told to upgrade to NAV 4. This is NAV 2009 SP1. Is there a way I can get around this?
0
Comments
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
2. Shut down all the services (NAV middle tier and NAV web-service).
3. Search for the record in the table 2000000071 "Object Metadata" that is linked to the object that throws the error and delete it.
4. Open your Object Designer and search for the object that's causing the error, open it in design mode and save & compile it.
5. Start all your services again
6. Try to reconnect.
This helped for me.
It seems that a connection keeps the old table structure alive in the cache and refuses to release it.
...
Everybody on-line.
...
Looking good!