Solved

Missing Reference - Converting from 97 to 2000, Excel into Access

Posted on 2002-05-13
7
162 Views
Last Modified: 2010-05-02
I have a VB program that exports Excel data into an Access database.
Our office just upgraded to Windows 2000 (we had 97).  The database converted perfectly - everything works fine.  However, I am having a problem with the export program (at least, I think that's what the problem is).
When I try to run it, it gives me a message something like "can't find object or library".  I did some research and found out that I am missing a DAO 2.5/3.5 Compatibility Library.  My question is, can I get this library from somewhere?  If I did, would that solve this problem?  Or should I update my code?  If I have to update my code, how do I know which lines are referencing DAO?  I am a relatively inexperienced VB programmer, so any suggestions will be helpful.  Thanks!
0
Comment
Question by:Mikayla
7 Comments
 
LVL 16

Expert Comment

by:Richie_Simonetti
ID: 7007586
Yes, you could install mdac software fro Microsoft.
0
 
LVL 16

Accepted Solution

by:
Richie_Simonetti earned 200 total points
ID: 7007588
0
 
LVL 16

Expert Comment

by:Richie_Simonetti
ID: 7007589
0
Why You Should Analyze Threat Actor TTPs

After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

 

Expert Comment

by:mani_m_in
ID: 7007864
Hi,
  MS-Access 2000 doesnot support the DAO 2.5/3.5 Compatibility Library. It supports only DAO 4.0 Compatibility Library. Try to update ur VB Code. You have to modify the code while Opening a Connecion Object. Change the DAO version 3.5 to 4.0 while opening a Connection object. I think this will solve ur problem.
0
 

Author Comment

by:Mikayla
ID: 7008545
That worked!  Thank you so much...I'll be able to sleep much better tonight!!
0
 
LVL 43

Expert Comment

by:TimCottee
ID: 7008570
mani_m_in right in the first part, wrong in the second. You are confusing the OLEDB provider 3.51 and 4.0 with the DAO library. The correct version for Access 2000 of the DAO library is 3.6 rather than 3.5 or lower.

To resolve the issue you should be able to uncheck the references to the 2.5/3.5 compatibility library and check the 3.6 library instead.
0
 
LVL 16

Expert Comment

by:Richie_Simonetti
ID: 7008582
Thanks for "A" grade.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Introduction While answering a recent question (http://www.experts-exchange.com/Q_27402310.html) in the VB classic zone, I wrote some VB code in the (Office) VBA environment, rather than fire up my older PC.  I didn't post completely correct code o…
If you need to start windows update installation remotely or as a scheduled task you will find this very helpful.
Get people started with the process of using Access VBA to control Excel using automation, Microsoft Access can control other applications. An example is the ability to programmatically talk to Excel. Using automation, an Access application can laun…
Show developers how to use a criteria form to limit the data that appears on an Access report. It is a common requirement that users can specify the criteria for a report at runtime. The easiest way to accomplish this is using a criteria form that a…

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now