The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I know. You are definitely right. I've ignored these so many times. Just this one time it got to me.
I think it got to me because I was really trying to have a simple conversation about an interesting thing I put a lot of work into.
Thanks for the input.
I'm developing a 64-bit app that interfaces with Access databases, which works fine with the 64-bit ACE drivers. However, due to some inexplicable co-mingling, you can't have 32-bit and 64-bit Access drivers existing on the system without 'tricking' Windows. This also works fine, until Windows update 'fixes' your trickery, forcing your 32-bit Office installation to repair itself and break your 64-bit drivers.
Some solutions are obvious, but stupid (switch to SQL, turn off Windows Update, force users to use 64-bit Office...) and I'd like to get Microsoft's official recommendation.
They're going to make me pay for that aren't they?
It's a consumer app - it'll be on people's machines with their whatever-version of Office. If they happen to have 64-bit Office (unlikely) it'll all work OK, but if they have our 64-bit plugin, and 32-bit Office (more likely) its a potential problem.
It's a plugin - if they have a 64-bit version of the host app, they need a 64-bit version of our product. Of course, we will have a 32-bit version too, but forcing the user to acquire a different 'bit-version' of the host app isn't ideal. Inevitably they will tend to ignore the requirement, and then complain about our app 'not working'.
It would all have been academic if Microsoft hadn't made their drivers mutually exclusive...
There is no problem matching bitity of host and plugin - the problem arises when that bitity is not matched by the installed version of Office. Not many people use 64-bit Office, so people using 64-bit host are likely to have 32-bit Office.
Yes - but that doesn't really help. The best I could do would be to refuse to install or give some kind of warning if the bitness of Office doesn't match the bitness of the host app - it doesn't solve the underlying problem.
I often refer to coding as "going underwater" because when you are concentrating on some feature or algorithm or whatever it's as if you become totally submerged by the challenge. You can't even hear other people talking.
Anyways, I recently had this experience while writing my book, Launch Your Android App (releases at Amazon.com on April 1, 2016 (and no, it's not an April fools joke).
An API Can Suck You Underwater
There's a feature in Android which supposedly allows you to share text (import text into your app which the user has selected in another app like the browser).