Developing in Access 2007, deploying on 2003

[JJSRich]

I've been recently upgraded to a PC with Office 2k7 on it, and am still responsible for maintaining the Access database. We've had some bother with my latest update. Basically I've needed to remove the references to the Excel 12.0 Object Library, and add in the reference to the 11.0 library on one of the Office 2k3 PC's, then distribute that. Since the export to Excel is quite important for some of our analysis, I would like to stop this from happening. Is there any way to easily write a backwards-compatable Access DB?

 

[randy700]

How about Save As from the Office button dropdown menu?


Randy

 

[JJSRich]

That doesn't carry the components with it. I know all about the whole Office 2007 file format debacle, and it really is a pain in the neck.

 

[MajP]

I know of no easy way to do it. You want to use as much late binding as possible, which makes writing code more difficult. Late binding will solve the issue with the reference to Excel. However, you will still need to test it in a 2003 environment. I have found that some of the new colors to not port over correctly such as getting a normal white background text bock becoming an black font on a black backgound.

 

[MajP]

http://www.granite.ab.ca/access/latebinding.htm

 

[JJSRich]

I thought there would be no easy way, Office is Microsoft's gravy train, after all. I will look in to the late binding, and see if it is applicable, and works.

 

[MajP]

I know of no "easy" organic way. However along with late binding you can write code that sets your references. So you deploy it without references and let the code set the references. There is lot of examples to do this.

http://msdn.microsoft.com/en-us/library/bb256558.aspx

But besides late binding and writing your own code, I do not know of any easier ways. There are 3rd party apps that do this.

 

[MajP]

As a disclaimer. I do not develop applications for commercial distribution. Most db's I make are for personal or limited use. You may need to get a second opinion from someone who does distribution of Access applications.

 

[JJSRich]

We don't distribute this app, it's in-house only.

 

[PHV]

The usual way is to develop into the lowest version.

Hope This Helps, PH.
FAQ219-2884
FAQ181-2886

 

[JJSRich]

Goodie. I get to develop into Office 2000 then, as we've got a few installs of that kicking around... not that they need to use the database now. If it becomes any more of a hassle, I swear I'm going to re-write it all in C# or PHP, like I wanted to do 2 years ago.