Late Binding tutorial?

[GBalcom]

Hello,
I've created a desktop application in Access 2013 that uses excel automation. This works great on my development computer, but it doesn't want to work on my production computer (which has excel 2010 on it. ) It barks at me about a missing reference for excel v15.

I've tried to do some homework on this, and it seems I may have used early binding, when late binding would be better in this situation. I'm still trying to wrap my head around this, so please be patient. It seems some people are using something called a "conditional compiler"? I think it may be a setting. How does this fit into the scheme of things? Can anyone provide a reference or tuturial to help me understand this?

I'm at home, but when I get in tomorrow I'll copy some of the code and post, to ensure I'm using early binding like I think.

Thanks!

 

[spikepl]

This really ain't rocket science. google

 

[pbaldy]

If it barks about a reference, it's probably early binding.

https://support.microsoft.com/en-us/kb/245115

 

[GinaWhipp]

Here's a nice article on Late Binding...
http://www.granite.ab.ca/access/latebinding.htm

 

[gemma-the-husky]

there may be other issues. The right way is to develop on the lowest version you will encounter - in this case A2010


basically, though, you declare the objects slightly differently. you can use all the normal excel methods, because they are part of the object you instantiate - but access doesn't know any of the constants, so you have to use explicit constants.