Joe4
MrExcel MVP, Junior Admin
- Joined
- Aug 1, 2002
- Messages
- 74,345
- Office Version
- 365
- Platform
- Windows
We are converting to Office 2007, and I have encountered some downright frustrating things that they have taken away in Excel and VBA.
1. FileSearch functionality gone (VBA)
2. Ability to save to a DBF (DB4) file (Excel and VBA)
Thanks to some people here, I got a workaround to item #1. And from my research on the web, I haven't found an Excel workaround for item #2. It looks like I will have to use Access to save to a DBF file. Not a big deal, as I am quite proficient in Access, just a pain in the neck in that I need to convert a bunch of programs.
The second item really irks me though. According to what I have read, it is "planned" obsolesence by Microsoft, as they determined that there is an out-dated functionality isn't really used anymore, though a simple search of the web clearly disputes that notion (as do many people in our office). Makes me wonder, do they do any research before making such crazy statements?
Anyway, venting isn't the only reason for this post (though it does feel good to get it off my chest), I also have a few discussion questions:
1. Has anyone found any other workarounds to item #2 that continues to use Excel VBA?
2. Does anyone know if there is any chance Microsoft might restore this feature in a future patch/release?
Thanks.
1. FileSearch functionality gone (VBA)
2. Ability to save to a DBF (DB4) file (Excel and VBA)
Thanks to some people here, I got a workaround to item #1. And from my research on the web, I haven't found an Excel workaround for item #2. It looks like I will have to use Access to save to a DBF file. Not a big deal, as I am quite proficient in Access, just a pain in the neck in that I need to convert a bunch of programs.
The second item really irks me though. According to what I have read, it is "planned" obsolesence by Microsoft, as they determined that there is an out-dated functionality isn't really used anymore, though a simple search of the web clearly disputes that notion (as do many people in our office). Makes me wonder, do they do any research before making such crazy statements?
Anyway, venting isn't the only reason for this post (though it does feel good to get it off my chest), I also have a few discussion questions:
1. Has anyone found any other workarounds to item #2 that continues to use Excel VBA?
2. Does anyone know if there is any chance Microsoft might restore this feature in a future patch/release?
Thanks.