NAV 5.0 NATIVE -> SQL Server : Compatibility Error
kash387
Member Posts: 111
I have used Migration FOBs for migrating native database to SQL Server 2005 and it done successfully.
Now, as per my client's requirement we have added too many fields in Purchase Header table.
Now, the client wants us to increase the length of those fields, but when I do that I got error like this:
A record may contain maximum of 4000 bytes of active fields in it.
So it doesnt allow me to increase the length. I know I can deactive a few fields by removing tick from enable field. But I dont want to do that.
I tried to change the length from SQL Server and made it of 250 (Varchar) whereas the NAV database contains that field as Text(30).
So when I run the purchase order form, I got the error that SQL Datatype is not compatible with NAV Datatype....
Is there any solution for this senario>>????
Thanks and Regards...
Kashyap
Now, as per my client's requirement we have added too many fields in Purchase Header table.
Now, the client wants us to increase the length of those fields, but when I do that I got error like this:
A record may contain maximum of 4000 bytes of active fields in it.
So it doesnt allow me to increase the length. I know I can deactive a few fields by removing tick from enable field. But I dont want to do that.
I tried to change the length from SQL Server and made it of 250 (Varchar) whereas the NAV database contains that field as Text(30).
So when I run the purchase order form, I got the error that SQL Datatype is not compatible with NAV Datatype....
Is there any solution for this senario>>????
Thanks and Regards...
Kashyap
Thanks,
Kashyap
Kashyap
0
Comments
-
I recommend to re-think the columns you have there - if they are really used, if they really needs to be so long, if they could be moved to another table which will have same PK etc. But I will never go the way of direct SQL modification or trying somehow hack NAV to accept bigger record...0
-
Ya... this is the requirement because for Import P.O., they need some fields which mentioned the details about product and insurance and finance and all the things.... Is it the good idea if I make a few fields deactivate???Thanks,
Kashyap0 -
kash387 wrote:Ya... this is the requirement because for Import P.O., they need some fields which mentioned the details about product and insurance and finance and all the things.... Is it the good idea if I make a few fields deactivate???
This doesn't mean they need to be in the same table.There are no bugs - only undocumented features.0 -
So in which table I can do these things....
If I am making a purchase order (import-outside country) and they want a few fields then in which table I can put those fields...????Thanks,
Kashyap0 -
Create a new related table as mentioned above.There are no bugs - only undocumented features.0
Categories
- All Categories
- 75 General
- 75 Announcements
- 66.7K Microsoft Dynamics NAV
- 18.8K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 610 NAV Courses, Exams & Certification
- 1.9K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 251 Dynamics CRM
- 103 Dynamics GP
- 6 Dynamics SL
- 1.5K Other
- 991 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 28 Design Patterns (General & Best Practices)
- Architectural Patterns
- 9 Design Patterns
- 4 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1K General Chat
- 1.6K Website
- 77 Testing
- 1.2K Download section
- 23 How Tos section
- 249 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
