Andy -

A word to the wise. If your customers are using Office 2000, you should be
developing in Office 2000. If you have a reference to an older object model and the
project is opened on a newer version, the newer version will be used instead. The
reverse is not true: your 2003 reference was not compatible with the older client's
2000 version.

It's possible, though a little flaky, to run multiple Office installations on one
machine. Things will work better if you install the oldest version first, and work
your way forward.

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

Andy wrote:

Hello everybody,

I formatted my notebook because it had problems.
Before I had Win2000 and Office 2000, now I have Win XP and Office 2003.

The problem is that I have various projects in which I used following VB 6
code to open dinamically Excel and write in.

"..
'I try open excel
Set XlsApp = GetObject(, "Excel.Application") 'look for a running copy
of Excel

If Err.Number < 0 Then 'If Excel is not running then
Set XlsApp = CreateObject("Excel.Application") 'run it
End If
Err.Clear ' Clear Err object in case error occurred.

On Error GoTo Error_Excel_Mng

...."

I have seen that recompiling (make Exe) and releasing the software on
customer's pc having Win 2000 and especially Office 2000 my program no more
work correctly.
I think because the vb reference is 'Microsoft Excel 11.0 Object Library'.

Our helpline says that I can't install Office 2000 after Office 2003.

I ask you which is the better solution that I can use.
I prefer not to return to have my laptop with previous versions vecchie or
to need another old pc.

Thank you very much.

Andy