Upgrade 4.0 db with 5.0 exe

Comments

• Options

  nunomaia Member Posts: 1,153

  2007-03-31

  first NAV 5.0 bug ?
  
  :shock:

  Nuno Maia
  
  Freelance Dynamics AX
  Blog : http://axnmaia.wordpress.com/

  0
• Options

  ara3n Member Posts: 9,255

  2007-03-31

  looks like it.
  
  A workaround is to backup all your tables. and import them afterwards.
  
  
  Edit.
  
  I Text compared the objects, and looks like
  Clustered=Yes is changed on all the tables in PK.
  
  I would still write a dataport to load the old data and time and check flag back.

  Ahmed Rashed Amini
  Independent Consultant/Developer
  
  
  blog: https://dynamicsuser.net/nav/b/ara3n

  0
• Options

  Waldo Member Posts: 3,412

  2007-04-01

  Is it possible that your previous database contained tables without clustered indexes?
  
  I know that when you use the Key virtual table to change the property, that the modified flag and date/time changes.
  You could write some code to change the property, and afterward changes the object record to the same datetime and modified status ... before you convert to 5.0... :-k

  
  Eric Wauters
  MVP - Microsoft Dynamics NAV
  My blog
  

  0
• Options

  ara3n Member Posts: 9,255

  2007-04-01

  Yeah a dataport can set the modified flag,date and time back

  Ahmed Rashed Amini
  Independent Consultant/Developer
  
  
  blog: https://dynamicsuser.net/nav/b/ara3n

  0
• Options

  David_Singleton Member Posts: 5,479

  2007-06-16

  ara3n wrote:

  I upgraded a db on sql and looking now at the object designer, all the table objects have modified flag checked, date and time changed.
  
  Bummer
  [-(

  
  If you do it this way :
  
  
  Dynamics User Group - Upgrade 4xx EXE to 5.00 with End User license
  
  Then it does not change the object flag. (Of course it also does not set the clustered flag), but the Backup?restore method, supported by MS also does not set this flag.

  David Singleton
  

  0