billroper: (Default)
[personal profile] billroper
This would be easier, I understand, if the version of our software that I was trying to compile was being compiled with Visual Studio 2010 instead of Visual Studio 2005. But it isn't and so here I am.

Microsoft goofed in a big way when they issued revisions to the MDAC (Microsoft Data Access Classes) with Windows 7 SP1 and Windows 2008 R2 SP1 that made applications that were compiled on those systems incompatible with earlier versions of Windows. *oops* And it took them a long time to figure out how to fix it. But a fix has been issued.

And if you're compiling your application on the newer versions of the OS, you need to include a line that says "#import "MSADO28.tlb" to be able to work on all supported versions of Windows.

Unfortunately, if you're compiling your application on an older version of the OS, you need to include a line that says "#import "MSADO15.dll".

These are notably different lines.

And we have a mix of machines where we do development and builds that have different versions of the OS installed.

I have figured out a way to work around this in Visual Studio 2005, but it's distinctly less than pretty.

*sigh*

Date: 2013-07-30 04:45 am (UTC)
From: [identity profile] tigertoy.livejournal.com
While slightly less than pretty, this was easy to do with 1980s development tools. I would hope we haven't had so much "progress" that it's really hard now.

Date: 2013-07-30 05:27 pm (UTC)
From: [identity profile] kevinnickerson.livejournal.com
"Not using the most current stuff? - You're dead to us." -- Microsoft.

Profile

billroper: (Default)
billroper

January 2026

S M T W T F S
     1 2 3
4 5 6 7 8910
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 262728293031

Most Popular Tags

Style Credit

Expand Cut Tags

No cut tags
Page generated Jan. 27th, 2026 03:39 pm
Powered by Dreamwidth Studios