PC User said:
Microsoft Excel 9.0 Object Library
Use late binding. Late binding means you can safely remove the
reference and only have an error when the app executes lines of code
in question. Rather than erroring out while starting up the app and
not allowing the users in the app at all. Or when hitting a mid, left
or trim function call.
You'll want to install the reference if you are programming or
debugging and want to use the object intellisense while in the VBA
editor. Then,. once your app is running smoothly, remove the
reference and setup the late binding statements.
Sample code:
' Declare an object variable to hold the object
' reference. Dim as Object causes late binding.
Dim objWordDoc As Object
Set objWordDoc = CreateObject(" Word.Document")
For more information including additional text and some detailed links
see the "Late Binding in Microsoft Access" page at
http://www.granite.ab.ca/access/latebinding.htm
Microsoft Common Dialog Control 6.0 (SP)
Microsoft Windows Common Control 6.0 (SP)
Use API calls for these.
How do you get rid of troublesome ActiveX Controls/references?
http://www.granite.ab.ca/access/referencetroubles.htm
Now these look like ugly code. However it's mostly a matter of
dropping in the wrapper API functions into a module and calling them.
Office 2007 references
Microsoft Excel 12.0 Object Library
Late binding again.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -
http://msmvps.com/blogs/access/