• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 358
  • Last Modified:

ADOX deployment problem under VB.Net 2003

Hello!

I have an application which relinks some tables in an Access database using ADOX 2.7.  Everything works fine in the development  environment.  When the setup package is run (on the same machine) and then the INSTALLED program is run, I receive an error "System.IO.FileNotFoundException: File or assembly name Interop.ADOX, or one of its dependencies, was not found." when it attempts to run the code which references the ADOX library

(with, for example...
        Dim ADOXTable As ADOX.Table
        Dim ADOXCatalog As New ADOX.Catalog
        Dim ADOConnection As New ADODB.Connection
).

The "detected dependancies" include "Interop.ADOX.dll" and the file is in the installation directory with the executable program.  The other installed dll's are ADODB.dll and InterOp.ADOR.dll.  

MDAC 2.7 is installed on the machine and works fine when the code runs in the development environment.

Does anyone have any ideas on what can be causing the problem or any additional steps I need to take to use ADOX from an installed program?

Thanks,

John

0
John_Crumley
Asked:
John_Crumley
  • 7
  • 7
1 Solution
 
Bob LearnedCommented:
When you say:

>>MDAC 2.7 is installed on the machine and works fine when the code runs in the development environment.

Do you mean that MDAC 2.7 is installed on the production machine or the development machine?  I would imagine that it is a dependency problem that you are having, because MDAC was not installed on the target machine.

Bob
0
 
John_CrumleyAuthor Commented:
Bob,

The problem is occuring on the development machine and on target machines.  Everything works fine within the IDE on the development machine but when I install the software on the development machine (by running the install app from within the IDE) I get the specified error.  It also occurs on target machines when MDAC 2.7 has been installed.

John
0
 
Bob LearnedCommented:
In your solution, what references do you have for ADOX?

VS.NET 2002 or 2003?

When adding ADOX reference, I don't have Interop.ADOX.Dll?  How did you get this?

Bob

0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
John_CrumleyAuthor Commented:
I am using VS.NET 2003.

The "Interop.ADOX.dll" is added to the "Detected Dependancies" of the install project when I add a reference to "Microsoft ADO Ext. 2.7 for DDL and Security" to the project and then "refresh dependancies".  It goes away when I remove the reference.  I will try excluding "Interap.ADOX.dll" and see what happens.

An interesting point is that ADO works fine in the installed program.  It is only the ADOX that has a problem.  This is one of the reasons I do not think it is an MDAC install issue.

John
0
 
John_CrumleyAuthor Commented:
Excluding "Interop.ADOX.dll" did not help.  Same error messagge.

John
0
 
Bob LearnedCommented:
I need to ask what you are using ADOX for?  Would it be possible to do it the ADO.NET way?

Bob
0
 
John_CrumleyAuthor Commented:
I'm using ADOX to relink tables in an Access database.  The tables reside in a database which is the data store for a 3rd party business system.  I link the tables and then extract data from the 3rd party system into mine so that it can be manipulated without any impact on the 3rd party system.

My understanding is there is no ADO.NET options for this and that I must use ADOX or DAO.  I think of DAO as dead so I picked ADOX.  I may need to switch over to DAO and see if I can distribute it.

John
0
 
Bob LearnedCommented:
I understand now.  You are right in the ADO.NET does not have the capability to link Access tables.

Have you ever used a Dependency Walker program to determine the dependencies for the .dll file?

Bob
0
 
John_CrumleyAuthor Commented:
Bob,

No, I have not traced the dependancies that way.  I think I will punt at this point and do it in DAO though I may scrap the setup project and start over to see if that makes a difference.

John
0
 
Bob LearnedCommented:
You should probably delete this question.

Bob "Cleanup Volunteer"
0
 
John_CrumleyAuthor Commented:
Ok...Thanks.
0
 
John_CrumleyAuthor Commented:
Ok...how do I delete a question?

It appears I say "please delete this question"?  If not, a helpful hint on where to go in the navigation structure to delete the question would be great!

Thanks,

John
0
 
Bob LearnedCommented:
Post a question in Community Support TA and ask for this question to be deleted.

Thanks,
Bob
0
 
GhostModCommented:
PAQed, with points refunded (500)

GhostMod
Community Support Moderator
0

Featured Post

Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

  • 7
  • 7
Tackle projects and never again get stuck behind a technical roadblock.
Join Now