|
There are isolated problems with current patches, but they are well-known and documented on this site. |
I think it’s because “Index” is a reserved word in vba, though I may be wrong….
Edited Later:
It seems I’m wrong after all 
I just actually tried it and it works fine for me.
Braddy
Why not use Foglio1 instead of “Index”?
You named the object for a reason, so why not get the most “Bang” 
for your “Buck” 
?
Foglio1 is NOT a key word, at least not in the American version of MS-Excel 2002.
Alternativly, you may need to give Excel a breathing space by not putting your code in the Workbook Open event. Maybe put the Worksheet….Open line in a module and call that module from the Open event.
This is from Excel 5.x and I am sure that it still is here since that time. Trust me as far as you can throw me, but it might make things work.
Wassim
Arrggg Braddy
I see foglio is an Italian word for Sheet. Arggg. OK do you think you may have a Localization issue? OK here it what I am saying:
Since MS-Excel comes in many versions that would support many languages, you maybe up against the fact that some objects are called different names in different language versions, so you will need a file, from the Italian version, I don’t remember its name, it might be the *.olb file, and this file tells you what objects are supported with the names in the language of the software.
Do this for me, run this code and see what you get:
MsgBox Application.International(xlCountryCode)
If you get 1 you are using the US Excel, if you get 39, you are using the Italian version, and you can check this
MSKB article 213833 – XL2000: Creating Macros for Different Language Versions for more codes.
You can also check MSKB article 211404 – XL2000: Foreign Object Library Files (.olb) for Excel Available to download your Italian *.olb files. You will need two, the Excel one and the VBA one.
As to the other part of my earlier post, the stuff about having Excel get a breathing room, well in old versions, and some times in new ones, the actions taken during the Open event of the workbook kinda tax the system and thus you want to have the least tasks in that event going on. Disregard for the time being.
Wassim
Braddy
OK yes, the consensus that the workbook may have become corrupted is becoming more and more evident, and this is something very normal, 
it happens to the best of us.
To run the code I sent you, simply goto the VBE, Visual Basic Editor, by pressing ALT+F11, for example, and copy and paste this line in between a Sub Somename() and End Sub pair.
Then position the mouse pointer some where between the Sub and End Sub lines, and press F5.
The workbook corruption should not prohibit you from adding this bit of code, and running it, unless it is that severe, in which case I would suggest that you get a fresh copy of the workbook from your backup set. You do have a BACKUP don’t you?
Did you have a chance to look at the MSKB articles I quoted?
Wassim
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
Notifications
