Office apps versioning issue

[John]

Hi

I have an access app that uses word and outlook and both are referenced in
the access app. The problem is that my client have outlook 2000 and word
2000 while my development machine has outlook 2003 and word 2003. How can I
package the app for distribution so that it installs fine at clients end?

Thanks

Regards

 

[Tony Toews [MVP]]

I have an access app that uses word and outlook and both are referenced in
the access app. The problem is that my client have outlook 2000 and word
2000 while my development machine has outlook 2003 and word 2003. How can I
package the app for distribution so that it installs fine at clients end?

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

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

 

[Scott McDaniel]

Hi

I have an access app that uses word and outlook and both are referenced in
the access app. The problem is that my client have outlook 2000 and word
2000 while my development machine has outlook 2003 and word 2003. How can I
package the app for distribution so that it installs fine at clients end?

In addition to Tony's suggestion, you should also remember to develop to the "lowest common denominator" ... if your
target/client environment hosts only Office 2000, then you must be sure that your code will work in that environment.
Many features of Office/Access 2003 are NOT available in 2000 (the Printer object, for instance) so if you've used any
02 or 03 specific features, your application will fail on a machine running 2000, even with late binding.

Testing in the "target" environment will reveal these problems. A good pre-deployment routine would include thoroughly
testing your app on a clean machine with your "minimum requirements" in place. In this case, that would be one with
Office 2000 installed. You can use an old PC that's been wiped clean and then built to those minimums, or you can use
virtual machine software. I use vmWare, but there is also Virtual PC from MS, which is now free:

http://www.microsoft.com/windows/downloads/virtualpc/default.mspx

Of course you must still have licensing for the OS and any other programs installed in VPC.


Scott McDaniel
scott@takemeout_infotrakker.com
www.infotrakker.com

 

[Aaron Kempf]

I woudl reccomend not using Access 2000 for any reason

I mean-- you guys shouldn't be supporting old versions of Access-- it's just
not cost effective

In addition to Tony's suggestion, you should also remember to develop to

the "lowest common denominator" ... if your

target/client environment hosts only Office 2000, then you must be sure

that your code will work in that environment.

Many features of Office/Access 2003 are NOT available in 2000 (the Printer

object, for instance) so if you've used any

02 or 03 specific features, your application will fail on a machine

running 2000, even with late binding.

Testing in the "target" environment will reveal these problems. A good

pre-deployment routine would include thoroughly

testing your app on a clean machine with your "minimum requirements" in

place. In this case, that would be one with

Office 2000 installed. You can use an old PC that's been wiped clean and

then built to those minimums, or you can use

 

[Guest]

Wow, try telling the companies who use Office 2000 that.....

Maurice

I woudl reccomend not using Access 2000 for any reason

I mean-- you guys shouldn't be supporting old versions of Access-- it's just
not cost effective