Looking for documentation about excel automation for Navisio

Resender
Member Posts: 119
Currently working on a project where we export to an excel sheet.
I encountered some problems due to diffrent versions of excel used, for instance our test enviroment still uses excel 2003 while our remote dev have 2010.
(With remote dev I mean we have some people of our company working on it as well but who are not on our main site)
We managed to get everyones automation working for all versions but are cursing on the lack of clear-cut ways/information of doing things.
Basically I'm looking for information/documentation that could show each of the functions and properties available in the excel automation and how they work.
Thank you
I encountered some problems due to diffrent versions of excel used, for instance our test enviroment still uses excel 2003 while our remote dev have 2010.
(With remote dev I mean we have some people of our company working on it as well but who are not on our main site)
We managed to get everyones automation working for all versions but are cursing on the lack of clear-cut ways/information of doing things.
Basically I'm looking for information/documentation that could show each of the functions and properties available in the excel automation and how they work.
Thank you
0
Comments
-
Microsoft has extensive documentation on the Excel object model in MSDN. Just google "Excel object model" and you should get a bunch of links into MSDN.0
-
That's indeed what I was looking for but I also have a 'problem' with it.
You got _Application and Application interface, both link to the same page but there is a difference.
In this instance the report used Application interface for the older excel versions, but when we tried this for machines we excel 2010 we got the following error:
'The variable XPAPPL::PROTECTEDVIEW is defined multiple times....'
We did not receive this error for the _Application interface, so their is a subtle diffrence that is not explained by the pages.0 -
When you search for difference between _application and application, you get a lot of hits.
What I've got out of it all was that, when problems occurs with application due to methods or functions having a same name/signature, use _application.
I'm guessing it is because it's a wrapper around the application which makes all the functions go one lvl deeper.0 -
Could Navision run as a virtual application count as a extra wrapper around this.0
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