Office XML on your 2.x 3.x or 4.x database

Marije_Brummel · 2007-04-03

You can use this cool functionality if you perform a technical upgrade of your database. This means only using the new runtime (fin.exe and server.exe) on your old business logic.

These are the steps to take after the runtimeupgrade

Implement Office XML in a Technical Upgrade

Codeunit 1

Copy the 3 functions from a 5.0 database

Name ID
LaunchApp 116
SelectStyleSheet 117
ManageStyleSheets 118

Objects

Copy these opbjects from 5.0 to your database

Type ID Name

Form 690 Manage Style Sheets
Form 691 Send-to Programs
Form 692 Import Style Sheet
Form 693 Program Selection
Form 694 Style Sheets
Codeunit 403 Application Launch Management

System Tables

Copy the values from system tables

2000000065 Send-To Program
2000000066 Style Sheet
2000000067 User Default Style Sheet

From a 5.0 database to your database

And your GO

One other advantage of doing a runtime upgrade is having support for Windows Vista.

A good step after this runtime upgrade is to do a functional upgrade to be fully prepared for 5.1.

Good Luck

kine · 2007-04-03

And do not forget to buy appropriate granule... or it is working with all licenses??? :-k 8)

Marije_Brummel · 2007-04-03

Hmm, good point. I've tested with a partner license and it works but with a customer license for 5.0 it does not. ](*,)

Does anyone know if it is :

a). A separate granule
b). A bug in the licensemodule
c). Something else

Otherwise you can always renumber. :-$

kine · 2007-04-03

I didn't found it in granule list. but:

1) it means, that there is no granule for this but you need to request refresh of license
2) It is in the list but I didn't found it
3) It is part of other granule

ara3n · 2007-04-03

hmm this was already posted a few days ago.

http://www.mibuso.com/forum/viewtopic.php?t=17452

Marije_Brummel · 2007-04-03

Oops :oops:

Did not read this post. Stupid me. At least we follow the same steps.

Waldo · 2007-09-25

One remark.
See that the appropriate security settings are added as well (for the new objects ... being:

Table 2000000065 Send-To Program
Table 2000000066 Style Sheet
Table 2000000067 User Default Style Sheet
Table 2000000068 Record Link
Form 690 Manage Style Sheets
Form 691 Send-to Programs
Form 692 Import Style Sheet
Form 693 Program Selection
Form 694 Style Sheets
Codeunit 403 Application Launch Management

8)

I was working on a blog post before I saw this thread ...

... luckily I didn't waste too much time

.

alsol · 2011-04-20

Hi,

Thanks for this great manual.

I tried it with an 4.00 SP3 database which we run with NAV 2009 SP1 client. Everything worked but as soon I add the new functions to CU1 the client crashed completly. Any ideas?

Best regards

Waldo · 2011-04-20

you manually added the functions? or with merging or fob import?

May be the function-id's don't align (should be the same)?

LaunchApp 116
SelectStyleSheet 117
ManageStyleSheets 118

ara3n · 2011-04-20

You can also copy and paste the functions and it will copy the same id's

livingdoll · 2011-05-20

alsol wrote:

Hi,

Thanks for this great manual.

I tried it with an 4.00 SP3 database which we run with NAV 2009 SP1 client. Everything worked but as soon I add the new functions to CU1 the client crashed completly. Any ideas?

Best regards

Hi Alsol,

Same thing happened with me. Did you find a solution for this?

Greetz
LD

ara3n · 2011-05-20

How did you add them? Did you copy and paste the functions?

alsol · 2011-05-20

Hi,

I added the functions by copying the whole function. And the function ID were the same. Unfortunately it still does not work.

Any ideas?

Best regards,
Felix

ara3n · 2011-05-20

export CU 1 and compare it to 2009 Sp1 and see if something is different. Also, I am assuming you have copied these from 2009 cronus db.

Office XML on your 2.x 3.x or 4.x database

Comments

Categories