References

[Ruben granados]

Hi, strange things are happening with my application when
installing in other computers. but not in all.. that why
i'm thinking it could be a references issue.
before giving the mde to user's I try it on other PC
having no missing reference. but could still be the case
to be a reference issue?
my references look like this (in this order)
Visual basic for Applications
Microsoft Access 9.0 Object Library
Ole Automation
Microsoft data access components installed version
Microsoft data formatting object library
Microsoft OLE DB Error Library
Microsoft DAO 3.6 Object Library
Microsoft Visual Basic for applications Extensibility 5.3
Microsoft Active X data Objects 2.5 Library
Microsoft Excel 9.0 Object Library
Microsoft ADO Ext 2.7 for DDL and security

Queries are not running properly, and also I get "Object
invalid or not longer set" when trying to open reports.
As I said, it only happens in some computers.. not in
every..

Thank you!

 

[Brendan Reynolds]

That's a lot of references. Are you sure you need them all? I'm fairly sure,
for example, that the Microsoft Visual Basic for Applications Extensibility
library would be redundant in an MDE, as an MDE includes no source code.
Some of those references could easily be missing on a target PC. The fact
that the MDE works on one test PC doesn't really prove anything except that
the test PC has the necessary versions of the referenced components
installed. You really need to do your testing on a clean install of the
earliest version of Windows and Office you intend to support.

The ADODB (Microsoft Active X Data Objects) and ADOX (Microsoft ADO Ext 2.7
for DDL and Security) references are among the most likely culprits - there
are (if I remember correctly) about 9 different versions of ADO 2.x now (2.0
to 2.8). The ADOX reference is a particular problem because while you can
have multiple versions of the ADODB library installed on the same PC, you
can, as far as I know, have only one version of ADOX, because all of the
versions use the same file name for the DLL.

If you have the Developer Edition of Office, you can use the Setup and
Deployment wizard to create an installation that will detect and include
dependencies, such as the version of the ADODB library referenced by your
application. But if you can get rid of unnecessary references, and test on
the earliest version of Windows and Office you intend to support, you may
well find that referencing the version of ADODB that is installed by default
in that configuration may be all you need to do.

 

[Guest]

No I don't know if i need them all. New on Access and this
is my first DB. Thanks for your quick response. I will
follow your advise =)

 

[Ruben Granados]

If the Microsoft Active X Data Objects and Microsoft ADO
Ext 2.7 for DDL security might be the culprits, can I just
copy the dll file from my computer and paste it in the
computers where the application is not working?

thx.

 

[Brendan Reynolds]

I don't think so, I think they'd need to be registered as well. But if you
have physical access to the target PCs, and the PCs have Access installed
(you're not deploying a runtime install) you can probably just change the
references to versions that are installed on those PCs. Just open any module
and choose References from the tools menu. Make a note of the references
that are checked. One at a time, uncheck those that can be unchecked (the
Access and VBA references can't). Try to compile the app. If it compiles
without any errors, the reference is not needed. If you get a compile error,
go back into References, scroll through the list to find the reference you
just unchecked, and check it again - you'll now be using the version that is
actually installed on that PC.

 

[Douglas J. Steele]

You definitely can't just copy the ADO/ADOX-related dlls. You need to
install the appropriate version of MDAC.

 

[Ruben]

Thanks a lot. I hope this is the reason why the DB is
doing such crazy things.. =(

 

[Ruben Granados]

Thank you all! The references were not the problem. I
forgot to set to nothing a catalog
Now everything works great!
Again thank you all!