MDAC Under Windows 7 x64 Home Premium

Forums › Microsoft Windows › MDAC Under Windows 7 x64 Home Premium

1 | 2

teasp00n

28 posts

Geek

#477282 3-Jun-2011 07:12

The procedure entry point ?ConvertExclusiveToShared@cReaderWriterLock3AR@@QAEXXZ could not be located in the dynamic link library MSDART.DLL

Thoughts?

gzt

17134 posts

Uber Geek

Lifetime subscriber

#477283 3-Jun-2011 07:15

btw, which platform are you compiling on? Is that the [win 7] x64 Pro, or something different?

teasp00n

28 posts

Geek

#477286 3-Jun-2011 07:20

Something different.

I'm compiling on Windows XP x86, Visual Studio 2008 and told it to build for x86.

It works on the following systems:

Windows 7 Professional x86

Windows XP

Windows Vista Home Premium x86

Windows 7 Professional x64 (my personal pc at home)

I do have Visual Studio installed on my home computer, that installs a slew of data access drivers doesn't it? Maybe I'll run it on there and use sysinternals to work out exactly what dll its using for odbc.

TwoSeven

1624 posts

Uber Geek

Subscriber

#477439 3-Jun-2011 14:49

This more of an aside than anything.

Might want to try creating an installer project to test and check dependencies. Typically I create a new solution based on the blank template (called xyz), then add my app project (xyz.FormsApp) and then a setup project (xyz.install).

The installer application(s) can be used for dependency checking and platform targeting.

Another thing, one can also leverage the microsoft provider model to get a list of providers and then use the SqlConnectionStringBuilder (System.Data) to create a connection string. This can be useful when one is referencing a local database.

Just some thoughts.

Andy

Software Engineer
(the practice of real science, engineering and management)
A.I. (Automation rebranded)
Gender Neutral
(a person who believes in equality and who does not believe in/use stereotypes. Examples such as gender, binary, nonbinary, male/female etc.)

...they/their/them...

teasp00n

28 posts

Geek

#477650 4-Jun-2011 03:01

After all that excitement it was a corrupt MSDART.dll.

Thanks for all the help guys

1 | 2