I'd start here--Chip Pearson's site:
http://cpearson.com/excel/vbe.aspx
> I am developing a user interface to handle their information stored in Excel
> 2003. Whenever I have new changes or I have a new version I want to export
[quoted text clipped - 5 lines]
>
> Thx

Signature
Dave Peterson
Gussie - 17 Oct 2007 14:19 GMT
I will read the code and take what I need.
Thanks Dave!
> I'd start here--Chip Pearson's site:
> http://cpearson.com/excel/vbe.aspx
[quoted text clipped - 8 lines]
> >
> > Thx
In addition to the code on my site, I would recommend that you consider
separating data from code and put all your code in a XLA or COM Add-In. Then
when a code change is required, you need distribute only the Add-In to the
users. The data would remain safely isolated from the code so there would
be no versioning problems, security problems and the like. The production
workbook that contains the actual data need not be updated or redistributed.
See http://www.cpearson.com/Excel/CreatingCOMAddIn.aspx for COM Add Ins and
see http://www.cpearson.com/Excel/CreateAddIn.aspx for XLA add ins.

Signature
Cordially,
Chip Pearson
Microsoft MVP - Excel, 10 Years
Pearson Software Consulting
www.cpearson.com
(email on the web site)
>I am developing a user interface to handle their information stored in
>Excel
[quoted text clipped - 6 lines]
>
> Thx
Gussie - 01 Nov 2007 19:58 GMT
Chip, that is actualy a better the way to go. I will look into that as soon
as I get a chance to do it. I am doing the interface as the user is entering
information -kind off changing the wheel on a moving vehicle.
Thank you so much guys!
> In addition to the code on my site, I would recommend that you consider
> separating data from code and put all your code in a XLA or COM Add-In. Then
[quoted text clipped - 15 lines]
> >
> > Thx