When you design and add-in, what is the best best process of developing and
add-in
that contain data in the worksheet of the *.xla file.

Questions 1
During the development of the Add-in, do I need to keep a copy of the add-in
in .XLS format or can I write code that will display the data in in .XLA
worksheet in order to modifiy the data unitl I complete the development.

Question 2
How to display the worksheet of an .XLA that contains data.

--
picasso

> During the development of the Add-in, do I need to keep a copy of the
> add-in
> in .XLS format or can I write code that will display the data in in .XLA
> worksheet in order to modifiy the data unitl I complete the development.

You can work directly in the XLA. There is no need to keep an XLS version.
In fact, that would only add to confusion.

> How to display the worksheet of an .XLA that contains data.

You don't. XLA's are hidden and you cannot (or should not not) display
anything from the XLA.

--
Cordially,
Chip Pearson
Microsoft MVP - Excel
Pearson Software Consulting
www.cpearson.com
(email on the web site)


"Jean-Marc" <(E-Mail Removed)> wrote in message
news:6001D236-A388-43ED-9312-(E-Mail Removed)...
> When you design and add-in, what is the best best process of developing
> and
> add-in
> that contain data in the worksheet of the *.xla file.
>
> Questions 1
> During the development of the Add-in, do I need to keep a copy of the
> add-in
> in .XLS format or can I write code that will display the data in in .XLA
> worksheet in order to modifiy the data unitl I complete the development.
>
> Question 2
> How to display the worksheet of an .XLA that contains data.
>
> --
> picasso

Let me clarify Chip's response.

>> How to display the worksheet of an .XLA that contains data.
>
> You don't. XLA's are hidden and you cannot (or should not not) display
> anything from the XLA.

You never ever want to expose the sheets of the add-in to the user (i.e., at
run time).

If you need to manipulate the data (at design time), select the ThisWorkbook
object under the add-in's VB Project, and in the Properties pane, change
IsAddIn to False. This makes the workbook visible, so you can manipulate it.
Change IsAddIn back to True when finished.

In general it is a more robust, more flexible, easier to maintain approach
to keep the data sheet in a workbook separate from the add-in.

- Jon
-------
Jon Peltier, Microsoft Excel MVP
Tutorials and Custom Solutions
Peltier Technical Services, Inc. - http://PeltierTech.com
_______