Error when changing field length in Nav-SQL

ccbryan63ccbryan63 Member Posts: 115
edited 2008-01-12 in Navision Attain
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

Comments

  • SavatageSavatage Member Posts: 7,142
    My thoughts are PUT IT BACK to the orginal size. Your changing it in 3 places but this isn't the end. You will find yourself changing it in dozens if not hundreds of places. Not to mention the upgrade headache that will lie ahead. Best to create a new field to hold this new code.

    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.
  • ccbryan63ccbryan63 Member Posts: 115
    Thanks for helping me convince him Harry. He's a reasonable man.
  • DenSterDenSter Member Posts: 8,307
    Are they running with 3.60 exe's on SQL Server 2005? That version is only supported for NAV 4.0 SP1 and up.
  • kinekine Member Posts: 12,562
    DenSter wrote:
    Are they running with 3.60 exe's on SQL Server 2005? That version is only supported for NAV 4.0 SP1 and up.

    Exactly... :-) Make a technical upgrade to NAV 4.0SP1 (best will be NAV 4.00SP3+latest update).
    Kamil Sacek
    MVP - Dynamics NAV
    My BLOG
    NAVERTICA a.s.
  • DriesDries Member Posts: 29
    What happend if you export the Item Ledger Entry as test file, then change the lenght of the Item No. to 30 and then import it into Navision?

    Will you get an error? give a try.

    NB: Make sure you're as administrator on Sql Server 2005.

    Cheers,
    Dries.
Sign In or Register to comment.