[AccessD] Missing references

Hi Jim et al

Also, don't forget that by verifying the references at launch, you have the option to catch and resolve possible errors before the user at some later point - while using your app - gets a bad experience with annoying error messages he/she can't handle at the spot anyway.

/gustav

>>> jimdettman at verizon.net 19-02-2007 14:41:07 >>>
Jim,

<<By checking the local references a program can then
adapt to its' current surroundings; but this requires a late-binding
design.>>

  How so?  If your dimming something as an object, you using late binding.
I don't know of anyway of changing from late to early without re-compiling
the program.   And if you use late binding, your carrying the performance
hit all the time.

Jim.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com 
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: Friday, February 16, 2007 2:36 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Missing references

Hi Jim:

The main reason for using late-binding is that an application developer does
not know what version of Word or Excel is on the clients' computer until the
application is run. By checking the local references a program can then
adapt to its' current surroundings; but this requires a late-binding design.

Just a comment
Jim