Backward Compatability? (Office 2003/2002)

[Static]

I have an app that uses Office 2K3.... but a user installing it says it tells her she need a diff ver of office....she has office 2002.. and i have 2003... how can i make this work without her updating?


EDIT:

IT said the message said this: The .NET framework installed but then said we needed Office Interop Access version 11.0.0 installed.
is there a way to include this? or should i have the user download/install it separately?

[JuggaloBrotha]

You're probably not using late biding when interacting with Office, if you switch your code to use late binded office objects then it'll work with multiple versions of office.

[Static]

i hate late binding... such a pain.
You dont get the nice popups with the available commands. lol

any other way around this?

[JuggaloBrotha]

None that I know of, but not using late binding means you're binding to a specific interop which means you're setting your program to a specific version of the app (office in this case)

[jmcilhinney]

Generally people develop and test their Office app with a reference and early-binding, then just remove the reference and switch to late-binding when they're ready to deploy.

You should also note that you don't have to allow late-binding project-wide. I was in a situation where I needed to use late-binding once and I set Option Strict On for the project and then I set it Off only in those files that specifically required it. I also created partial classes and set Option Strict Off in only one of them and put only the members that specifically required late-binding in that code file.

[Static]

ok, im stuck on this one part switching to late binding

I need to import a delim file... the import the data, and delete the file

AC.DoCmd.TransferText(Access.AcTextTransferType.acLinkDelim, , "NIA_Temp", "C:\NIA_Temp.csv", True)

????