.NET build error-Could not locate assembly

I'm tryinig to build a .NET web site from the code provided by another developer in VS2005.  I'm encountering this error:

Could not resolve this reference. Could not locate the assembly "dao, Version=10.0.4504.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.

I've looked for DAO-related files and I've found a DLL that's version 3.60.9512 . . . I'm guessing the original developer had a much earlier verion of something like Access or another Microsoft Office product on his machine.
Can anyone provide any advice on dealing with this . . . ?  Let me know if I should provide more information.  Thank you!
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Daniel Van Der WerkenIndependent ConsultantCommented:
So this other person had a reference set to a DLL on his system that you don't have.

If you're not using this DLL, then simply remove the reference from your project.  In the solution explorer, click on the [+] next to References.  You should see a list with:

You'll probably notice one with a warning symbol over it.  Right-click it and remove it.  See if you can build then.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
eggejmgAuthor Commented:
Sorry to be late getting back to you--I wasn't in the office over the weekend.  I did find the reference with the warning symbol.  Removing it killed the error,  I'm not sure if the original developer had anything going on in the code that needed that reference, though, so I'm not sure what the effect will be.  Is that somethinig I'd only know at run time?  Of course, until I can actually run it, I guess it would've been impossible to know anyway . . . Any recommendations on dealing with the matter?  I usually work with PHP and I'm feeling my way around this .NET stuff, so thanks for the help; I appreciate it.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Editors IDEs

From novice to tech pro — start learning today.