Test your custom form in a standalone environment with Outlook 2019 (32-bit) on Windows 11 plus necessary registry settings. If it works smoothly, you have your target version. Confirm all external dependencies of your form (Word interaction, any COM objects, ActiveX/Forms2.0 controls) are still supported. Plan a migration strategy: Even if Outlook 2019 works now, you should start planning to rebuild the form for newer platforms because the support window is narrowing (VBScript deprecation, changes in Outlook UI). If you must stay long-term and avoid migration cost, lock the user on a version you know works (and do not upgrade Outlook or switch to “New Outlook”).
Migrate Outlook 2007 custom contact form to Outlook Classic 2024 (or last version that supports it?)
Greetings, all. Not sure why "Outlook" is missing from child tags list above--site admin, please fix.
I built a custom contact form for a client 25 years ago originally for Outlook 2000, that leverages Forms 2.0 controls and extensive VBScript to interact within the form itself and with Microsoft Word. It's still functioning in Outlook 2007 on Windows 11 (after re-enabling VBScript for the form courtesy of this article: https://support.microsoft.com/en-us/office/custom-form-script-is-now-disabled-by-default-bd8ea308-733f-4728-bfcc-d7cce0120e94)
I can still make changes to the underlying code and it still works in Outlook 2007, but I was unable to get it working in Outlook Classic 2024. I believe I saw that Outlook Classic 2024 does NOT support Forms 2.0. What is the last version of Outlook to support Forms 2.0? 2016? Would 2019 support it? Outlook 2007 still works, but it's a little quirky.My next question is: my client purchased Office Home & Business 2024, but missed everything since 2007. Who would I talk to at Microsoft about arranging a product key and a download of Office 2016, or whatever last version supports her form? It's not worth rebuilding this project using different stuff at this stage.