One place I worked the CAD software used Excel for editing table daat. When we loaded Office 2003, Excel would not link back into our version of CAD. We had to do separate install of Excel97 and chnage the configuration settings on the CAD software to find it.
Had the same issue with 2007 and another CAD package, where the CAD would not work at all with Excel 2007 because of the default XML file names. IT director said just do a Save As. Took about 15 emails and a couple of hours to finally get it sunk into her head that solution would not work because the CAD software was looking for .xls formatted files.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Well many people seem to think that the new menu system is the work of the devil, although I don't mind it myself, but apart from that, if you want to use VBA with graphic objects (including charts) there are 2 good reasons for having an earlier version installed:
1. The 2007 macro recorder does not record anything you do to graphic objects, including charts.
2. Thare have been some significant changes to the object model for various shapes. Arcs for instance are defined differently in 2007 to earlier versions.
Even if you don't do any VBA programming with shapes and charts it is a good idea to check out any applications written in 2007 with an earlier version.
looslib - You know you can set the default save format in 2007 to .xls (97-2003 format)?
I have one computer with 2000 and 2007 and another with 2003 and 2007 and have no problems. On the same drive in both cases. I associate all Excel files with 2007, and if I want to run the earlier version I start it up without a file, then either double click on the file name, or use the Excel menu.
Yes we were aware that the default could be set, but it didn't matter to the CAD program. We could launch Excel 2007 from the CAD app, but the updates would not be written back to the CAD app when we exited Excel.
"Wildfires are dangerous, hard to control, and economically catastrophic."
Thank you all, I'll keep my eye on the comments. I am getting a new computer with Office 2007, but at the same time I will need to keep compatibility with 2003. There're some differences in VBA which prevent files to run properly on the new version.
>>
There're some differences in VBA which prevent files to run properly on the new version.
<<
VBA hasn't changed (as far as I know), and I don't recall having any problems getting any of my old macros to run in 2007, other than the fairly esoteric change to arc shapes that I mentioned previously.
But I do agree it's a good idea to have an earlier version installed.
Doug,
I encountered the following problem. The name of automation library for Solver has changed from solver.xla to solver.xlam. As a result Excel 2007 cannot find proper library and gives an error. The problem is easily fixed by changing the reference.
Thanks so much for posting the bit above about the solver. I had the same problem however I was told VBA was taken out and that is why it wouldn't work in the new Excel. So I gave up and refused to buy the latest office package recently when I bought my new computer. I installed office 2003 I think. I really hate that ribbon. I much prefered to be ablt to customize the toolbars and place them where they benfited me the most.
I discovered a few good things about Excel 2007:
- the files are half size of 2003 (if you care)
- it runs properly on Windows 7 (2003 does not, the worksheets within the same workbook become kind of transparent)
- it checks for errors in the formulas and names
- charts are much better
- drawing tools more extensive
- the ribbon is Ok if you have time to learn it (we will have to anyway).
I recorded a macro using Solver in Excel 2000. Now, i get an error, "Can't find project or library". I got upgraded to Excel 2007 and other peolple in our office use 2003. Yes, the Solver addin is loaded on all of the machines.
1. How do I change the VBA macro to make Solver work in Excel 2007?
2. Can I make the same xls file work for computers running Excel 2000, 2003 and 2007 as long as the appropriate Solver addin is loaded?
I need some simple directions to make this work! I am NOT a VBA wiz. Thanks all.
Steve - on each machine where the macro isn't working, go into the Visual Basic Editor (Alt-F11), select Tools-References from the main menu, and make sure that SOLVER has a tick next to it.
I'm not sure if this can be automated. I don't think so, but I'll check.
On the 2007 version, I went into the Visual Basic Editor (Alt-F11), select Tools-References, then I unticked MISSING:Solver.xla and ticked Solver and it works great now.
On the 2003 version, I had to untick MISSING:Solver.xla and manually run just the Solver, then I could go back and tick Solver. The VBA macro runs now, but the results are way out in the blue.
