With the help of several people on VBAX, I was able to get an application that updated and printed a Word document with Excel-calculated variables. This code is now working in three forms. The first form takes the data and prints a Word document using each data row in the spreadsheet. Version 2 prints only the "selected" row. Version 3 saves this Word file as opposed to printing it. The previous versions create the Word document, print it, then throw it away.
The 4th version was to create the Word document (like Ver 3) but only for the selected row (like Ver 2).
I use Excel 2000 (object library 9.0?) here and Excel 2003(object library 11.0) on my other PC. I often email the .xls files between these systems so that I can work on this problem from either machine.
Now my code will not compile, and it is giving me strange errors and indicating that Word is missing "Object library 11.0". When I attempt to
compile this new routine, VBA apparently comiles everything in this sheet (there are several routines) and it indicates errors in some of them also. These routines worked before. On Friday, I did send the .xls to the XL2003 machine so I could add data and write this 4th routine.
My intuition tells me that some piece of code compiled at the XL2003 machine has referenced a routine that is only present in XL2003. So when I try to compile on XL2000, I get this "missing object".
My understanding was that VBA is an interpreted language, so it should not be trying to use 11.0 object libraries in a 9.0 system.
What do I do about this? I'm pretty sure that there is no new feature in XL2003 that my code uses. I did this joint development platform (XL2000 and XL2003) on many other programs. How can I prevent this?