First, did the checks I suggested previously work?

If you have set a reference in your vb6 to Excel 10, there may indeed be
problems running in XL2000. I doubt the Windows version is relevant unless
you are using some API not available in earlier versions.

I assume you have access to the vb6 project in XL2K as you say you can see
where the code fails. Why not rename a backup of the project, delete any
missing ref's set the correct ref to Excel. With Excel closed, run the
project with F5, open Excel & your file and set the newly named ref to your
vb6 project. Run the code from vba and step through. If this works, rename
as original and compile. This new dll should now also work in the later
version - probably!

Presumably you fully declared oXL as Excel.Application. Depending on what
else you are doing it might be possible to remove all ref's to Excel and
declare oXL as Object.

Regards,
Peter T

"Sirhc M" wrote in message
ups.com...
Would there be any issues if:

a) The .dll VB6 file was compiled using Excel 2002,

and

b) I'm applying the .dll for use in Windows NT / Excel 2000?