[AccessD] Missing references

<<<
Having resolved it once, the app will 
behave as if it were early-bound thereafter.
>>>
Arthur,

You probably meant VBA's/VB6's or VB.NET's 

With
====

Operator?

For "With" operator - yes, it was written somewhere that if you use e.g.

Dim wapp as object
Set wapp = CreateObject("Word.Application")
Dim wdoc as object
Set wdoc = wapp.OpenDocument(....)
...
With wapp.Selection.Font
   .Size = ...
   .Bold = ...
   .Italic  = ...
...

Then wapp.Selection.Font will be saved as internal object reference and it
will not be recalculated for wapp.Selection.Font.Size,
wapp.Selection.Font.Bold, wapp.Selection.Font.Italic, ... etc.

Although the next usage in the code of

With wapp.Selection.Font

Code construct, even in the same function will result in several late-bound
"round-trips" via IDispatch COM interface proxy-stub boundaries to
dynamically recalculate actual target object reference...


--
Shamil
 
-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Robert
Sent: Saturday, February 17, 2007 5:55 PM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Missing references

Interesting thread.. I have not seen it mentioned that if you early bind to
an early version, Access will "re-reference" to any later installed version.


 This of course this does not work if the user has an earlier version or no
version at all installed ;-)

Robert

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

Quite right, and insofar as you resolve the late-bind issue asap, then such
binding shall not impede the subsequent performance of your app. Having
resolved it once, the app will behave as if it were early-bound thereafter.
 
A.


----- Original Message ----
From: Jim Lawrence <accessd at shaw.ca>
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
Sent: Friday, February 16, 2007 2:36:22 PM
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
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com