Ahh, I actually forgot about INNO. I downloaded a copy of it a couple
years ago but I don't remember checking it out.

The last place I worked at we used Wise and I was lucky enough to have
my own dedicated install machine that I could "Ghost" a fresh new copy
of the OS every time I wanted to test a new install package. That was
a great help but installs were still torture.

That company went TU in 2000 and I haven't worked since then. (that's
why I'm thinking about Excel) That's why I haven't taken the time to
get up to speed on the .NET stuff.

Thank you,

Don

On Thu, 23 Feb 2006 07:38:54 -0000, "RB Smissaert"
wrote:

Using INNO.
Free as you probably know and works very well.

RBS

"Don" wrote in message
.. .

Hi Chris, and all who have taken the time to answer.

I've programmed in all VB versions since 3.0 and ASM, Basic, etc
before that. I'm not really up to speed on .Net though. But, building
installation packages is one of my least favorite things to do. That's
likely not to be a problem for those of you that are creating Excel
applications for your own use but . . .

For those that are creating apps for others, are install packages
often needed or does the normal Office install suffice? How do you
handle the installation of any dll's, Db's, or? Do you do onsite
installs yourself or do you give complete install packaes to your
clients?

Your experience will be helpful to me and will be appreciated

Thank you all again for being willing to help.

Don in Redmond


On Wed, 22 Feb 2006 00:04:30 -0800, Chris Marlow
wrote:

Don,

Doing Excel work you are close to the user. It can be frustrating as 'big
systems' events can pull the carpet from under your feet & trying to
untangle
spaghetti that other 'developers' have built in the past can be a
nightmare
... however that also suggests that there is some mileage in it as (at
least
one strand to) a career.

Regards,

Chris.