Hi. My client is running US 3.01.B (3.60) with SQL 2005. He has suddenly decided after several years on Navision that he needs the Item No. field lengthened to 30 spaces. OK, using Object Designer to make the changes in table 27 Item and 28 Item Price was no problem. But when I try to do the change on 32 Item Ledger Entry, after going through redesigning the keys, it gives the following error:
2460,"01000",[Microsoft][ODBC SQL Server Driver][SQL Server] The ALL permission is deprecated and maintained only for compatibility. It DOES NOT imply ALL permissions defined on the entity.
This is just from changing the field length and then close/compile. There are around 200,000 records in 32 Item Ledger Entry.
I would appreciate any thoughts.... Thanks!
Chandler
0
Comments
If you are really serious about this you need the Developers toolkit to see everywhere where item.no is used. in reports, codeunits , etc even when item is moved to a variable in some code somewhere where the variable is size 20. You will get errors all over the place.
a 30 digit item no. I'd hate doing order entry at that place.
Personally I think Item numbers should be simple numbers - there are plenty of other fields that hold all the descriptive info.
You could create the new field "Item No. 3" and make that the altserachfield of the item no. this way either/or the new # or the item # can be used. Then your task is just adding the new field where it's needed. not everywhere.
I wouldn't even think of it for the description field - but I can understand. The "No." field ouch! You can do it his way & your billable time will probably get you a new yacht or convince him to do it another way and win his trust.
my 2 cents.
http://www.BiloBeauty.com
http://www.autismspeaks.org
RIS Plus, LLC
Exactly... :-) Make a technical upgrade to NAV 4.0SP1 (best will be NAV 4.00SP3+latest update).
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Will you get an error? give a try.
NB: Make sure you're as administrator on Sql Server 2005.
Cheers,
Dries.