OUAU should now work for all Office versions, and you can select the Office version (if for some reason you have partial Office installations) and it will reread and write the appropriate registry-entry.
Changes
To do
I tried ouau here at work, and we’re using Office 2002/XP. It finds the correct Office version, I’m able to make changes to the blocked extensions, which I can verify by restarting the program: it finds the new settings. But the new registry-setting resort no effect: right-click and send-to-mail-recipient of a unblocked extension (e.g. .EXE) still results in Outlook saying that the attachments are potentially unsafe. What’s going on here? Something to do with (group)policies?
Update: I think I already know: Exchange administrators can add/remove Level 1 and/or Level 2 extensions within the Exchange-server settings. This can not be overruled by the Outlookclient. So, I guess I’ll have to find another way to test other Office versions.
Yesterday I was working on an application (not WRap) that works with RTF documents. I load them into a RichViewEdit, and the user has the ability to do basic editing. To enable full-scale editing, I thought it would be nice to have a button that started Word with the appropriate document. So far so good.
Word opens, the document is loaded, document can be amended, saved, whatever. Exit Word. Oh my, I have to reload the document into my RichViewEdit. Easy. But…hey…wait a second. How do I know if the user is done editing in Word?
[Google searching heard in the background]
I found this page that basically has the answer. And indeed, basically it works. The program starts Word with the correct document, and if I close it, I’m back in my application. But…whenever I change the document and close Word (Do you wish to save…blablabla) something goes wrong. Word does not close, and I have to close it via CTRL-ALT-DEL. I can’t figure out what goes wrong, since the flow works whenever I don’t change the document. What’s the difference?