"This file was created in a pre-release version of Word 2007 and cannot be opened in this version."
I an error someone else gets when trying to open an excel macro enabled document on their 2007 version. They have successfully opened files from my 2007 word and another excel file (no macros). Any solutions?
Update:their system tells them my excel macro enabled document is corrupt and they try to recover it and that error comes up.
Copyright © 2024 Q2A.ES - All rights reserved.
Answers & Comments
It could be several things:
1. Is the version of Word that your document was created on a beta version? That means that you got the version of Word before Word 2007 was officially released. So it was a test version and test versions often normally don't have all the bugs worked out yet. So one of those bugs that wasn't worked out could be the problem.
2. Excel 2007 is very very picky about macros. In many ways it doesnt' really like them. And I think Microsoft kind of did that to avoid viruses from Excel macros. The .xlsx file format will not handle Excel macros. Yes, you can write macros in it. But when the person tries to open the file with macros, it doesn't want to work. The .xlsm file format is made to handle macros. So you may need to save the file as a .xlsm file. The old Excel 2003 default file format of .xls files could handle macros. In Excel 2007, I think Microsoft split the file types up into different formats for security purposes. I eventually look for them to try phasing the .xls file type out.
3. Another thing Excel 2007 is picky on is the Macro Security. The file folder that contains the file with the macro really needs to be listed on Excel's Trusted Locations. You can specify trusted locations under Excel Options. And another thing that probably needs to be done is to digitally sign the macro. This is where it really becomes a pain in the butt. If you digitally sign a macro, only your computer will trust it. Other computers with Excel 2007 won't trust it unless you get a digital signature from a specific group of companies stating you are a Trusted Publisher. And I think you have to pay for that. That is a good policy for macros from a publisher you don't know. But if say for instance a co-worker in your office creates the macro and you know you can trust them, it becomes a huge obstacle to use that macro. There needs to be a way to state "the macro came from this user" and then you can specify the names of certain people who create macros in your office that it's ok to accept them from. So if Bob Smith in my office creates a macro and I trust all macros from him, he doesn't have to use a third party company to be a trusted publisher.