Trivia Technical Question Regarding Update process

ManosA
Member Posts: 40
Hi all.
I have the following question.
When I try to update from one version to the next I follow this procedure:
!! A: open the DB with the version .exe that I want to convert it to.!!
B: export objects.
C: check them with the devtool.
D export the objects from the tool and into the DB in A.
My question is: what exactly does Navision do to the DB when I open it
with a higher version EXE (i.e. a 4 SP1 DB opened with a 4 SP3 exe).
Can anyone tell me what is converted and why this is needed?
Also if anyone knows exactly what the zup files stores plz elaborate.
(I know it is a snapshot of the interface but I think it holds more
information than that).
Thanks in advance for the reply.
I have the following question.
When I try to update from one version to the next I follow this procedure:
!! A: open the DB with the version .exe that I want to convert it to.!!
B: export objects.
C: check them with the devtool.
D export the objects from the tool and into the DB in A.
My question is: what exactly does Navision do to the DB when I open it
with a higher version EXE (i.e. a 4 SP1 DB opened with a 4 SP3 exe).
Can anyone tell me what is converted and why this is needed?
Also if anyone knows exactly what the zup files stores plz elaborate.
(I know it is a snapshot of the interface but I think it holds more
information than that).
Thanks in advance for the reply.
0
Comments
-
ManosA wrote:Hi all.
I have the following question.
When I try to update from one version to the next I follow this procedure:
!! A: open the DB with the version .exe that I want to convert it to.!!
B: export objects.
C: check them with the devtool.
D export the objects from the tool and into the DB in A.
My question is: what exactly does Navision do to the DB when I open it
with a higher version EXE (i.e. a 4 SP1 DB opened with a 4 SP3 exe).
Can anyone tell me what is converted and why this is needed?
Also if anyone knows exactly what the zup files stores plz elaborate.
(I know it is a snapshot of the interface but I think it holds more
information than that).
Thanks in advance for the reply.
There are two types of conversions.
For versions where there was no database structure change, then the conversion process simply sets a flag to know what version you are now using.
If there was a change to the structure of the database e.g. ver. 2.10 to 2.50) then the system goes though and makes those changes to the Database. In this case it is obvious why the conversion flag is necessary.
In the first case, the reason for the flag, is that newer versions of Navision nearly always have new properties available, these are stored in the database, and form that point on, and modifications to the objects would cause a problem if you opened them with an older version. This is why the flag is necessary.
Its very easy to tell which is happening, since the first takes a second or so, the second can take hours.David Singleton0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K 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
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions