I can't speak 100% towards that but I doubt it would work as nobody else I've found has been able to make it work short of doing what I originally said. You can certainly try it and see. But I doubt it will work.
I can't speak 100% towards that but I doubt it would work as nobody else I've found has been able to make it work short of doing what I originally said. You can certainly try it and see. But I doubt it will work.
Well Bob.... (drum roll....) I just received a Win 7 SP1 / Office 2010 test computer this morning. My application developed on Windows XP / Office 2007 works BEAUTIFULLY on the newer levels of code.
I used the technique of only compiling the database the first time through my procedure, then I skip over the Compile instruction until the file size stops changing. Absolutely NO issues running the database file prepared that way on the Windows XP / Office 2007 machine. So apparently deploying the completely decompiled database file was a viable solution to this compatibility break that MS caused.
Office 2010 is the 32-bit version.Windows 7 is 64-bit.
All bindings came up correctly - no adjustments necessary.
I have checked the TreeView OCX control and that works as expected. I included the "Microsoft Windows Common Controls 6.0 (SP6)" version of the OCX originally.
