to continue the saga from my previous post (excel event binding), the custom application i wrote for my client is now running happily with excel 2003 after implementing those new event handlers to satisfy excel 2003. so far so good. but that is not the end of the story.
new computers at my client site come with office 2007. (i don't know where you can buy office 2003 anymore.) excel 2007 again has some new events that need to be handled:
after adding these event handlers, excel 2007 ole automation has no problem.
however, my client application manipulates a lot of dbf files. (please don't ask me to upgrade the dbf to some sort of sql databases, as in my client's case it does not make sense -- trust me! 🙂
i found out some features of the app which automate excel to save in dbase iii format do not work anymore, and after some googling, i became aware that excel 2007 cannot save in dbf format any more.
haha, it comes to a dead end.
on a side note, in the past, when i want to automate excel, i just start up excel and record a macro of the actions i like to do, and then view the auto-generated macro to retrofit the code into vfp. sweat and easy.
i tried to do the same in excel 2007, say inserting a picture into a doc, and guess what, the recorded macro is empty. reading the help file it says navigations in the ribbon bar will not be recorded. (to tell you the truth, i am a bit shock when i read that :p) unfortunately, i don't know how to insert a picture into a doc without using the ribbon bar.
so i have to record a macro in excel 2002/2003 and then try the generated code with excel 2007 to see if it works or not. is there an easier way?
and of course, the idea of using excel to repair a dbf i blogged about earlier on does not work any more...
why things become so difficult in excel 2007? or is it just me? 🙂
btw, i am using vfp9 sp2.