Late Binding??

**Douglas J. Steele** · Nov 13 '05, 08:21 AM

Re: Late Binding??

Yes, that's late binding.

--
Doug Steele, Microsoft Access MVP

(no e-mails, please!)

"PC Datasheet" <nospam@nospam. spam> wrote in message
news:1dAPd.1136 6$oO.1502@newsr ead2.news.atl.e arthlink.net...[color=blue]
>I have this:
> Dim Cbr As Object
> Dim Ctl As Object
> Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
> Set Ctl =
> Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth")
> Is this considered late binding? If not, what needs changed?
>
> Thanks!
>
> Steve
>
>[/color]

**MacDermott** · Nov 13 '05, 08:21 AM

Re: Late Binding??

I stand corrected.

In some earlier threads, I'd said you needed to use CreateObject in this
case.
For some reason, I thought that you needed the Office Objects Library to
access CommandBar items programmaticall y. I just tried that out and
realized I was wrong on that.

I've lost track of who the OP was on this -
the issue seemed to be running this code on machines using different
versions of Access.
There was a reference to a specific version of the Office Objects
Library; it would still be my guess that this reference would not port well
to an earlier version of Access.
If this reference is not needed for other reasons, it should be removed.
If it's needed somewhere else, that place is probably where we need to
look for the problem.

- Turtle

"Douglas J. Steele" <NOSPAM_djsteel e@NOSPAM_canada .com> wrote in message
news:zMqdnficXr 3o15LfRVn-qg@rogers.com.. .[color=blue]
> Yes, that's late binding.
>
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
>
>
> "PC Datasheet" <nospam@nospam. spam> wrote in message
> news:1dAPd.1136 6$oO.1502@newsr ead2.news.atl.e arthlink.net...[color=green]
> >I have this:
> > Dim Cbr As Object
> > Dim Ctl As Object
> > Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
> > Set Ctl =
> > Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth")
> > Is this considered late binding? If not, what needs changed?
> >
> > Thanks!
> >
> > Steve
> >
> >[/color]
>
>[/color]

**Steve** · Nov 13 '05, 08:22 AM

Re: Late Binding??

<>
You do if you use:
Dim Cbr As CommandBar
Dim Ctl As Commandbar.Cont rol
I have Office97, 2000 and XP installed and only have Microsoft Office10
Library in my references. Apparently when later versions of Office are
installed, they remove previous versions of the Microsoft Office Library.
I'm creating an Access97 application that needs to manipulate a commandbar
and the controls on the commandbar. That's the reason for all my questions.
The end user of this application will only have MS Office97 installed and
thus Microsoft Office 8 Library in his references. Since I don't have that
reference, I went to late binding with:
Dim Cbr As Object
Dim Ctl As Object

<<it would still be my guess that this reference (Microsoft Office10
Library) would not port well to an earlier version of Access.>>
I think you are very right about this! Upon closer examination, the path to
Microsoft Office10 Library on my computer is:
C:\Program Files\Common Files\Microsoft Shared\Office 10\mso.dll
I presume that the path to references is carried with the database for all
checked references. Therefore, I must assume that the other machine would
never be able to find the Microsoft Office10 Library (mso.dll) because it is
an Office 8 machine and would not even have an Office 10 folder.

Steve

"MacDermott " <macdermott@nos pam.com> wrote in message
news:0UKPd.1162 2$oO.5794@newsr ead2.news.atl.e arthlink.net...[color=blue]
> I stand corrected.
>
> In some earlier threads, I'd said you needed to use CreateObject in this
> case.
> For some reason, I thought that you needed the Office Objects Library to
> access CommandBar items programmaticall y. I just tried that out and
> realized I was wrong on that.
>
> I've lost track of who the OP was on this -
> the issue seemed to be running this code on machines using different
> versions of Access.
> There was a reference to a specific version of the Office Objects
> Library; it would still be my guess that this reference would not port[/color]
well[color=blue]
> to an earlier version of Access.
> If this reference is not needed for other reasons, it should be[/color]
removed.[color=blue]
> If it's needed somewhere else, that place is probably where we need to
> look for the problem.
>
> - Turtle
>
> "Douglas J. Steele" <NOSPAM_djsteel e@NOSPAM_canada .com> wrote in message
> news:zMqdnficXr 3o15LfRVn-qg@rogers.com.. .[color=green]
> > Yes, that's late binding.
> >
> > --
> > Doug Steele, Microsoft Access MVP
> > http://I.Am/DougSteele
> > (no e-mails, please!)
> >
> >
> >
> > "PC Datasheet" <nospam@nospam. spam> wrote in message
> > news:1dAPd.1136 6$oO.1502@newsr ead2.news.atl.e arthlink.net...[color=darkred]
> > >I have this:
> > > Dim Cbr As Object
> > > Dim Ctl As Object
> > > Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
> > > Set Ctl =
> > >[/color][/color][/color]
Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth")[color=blue][color=green][color=darkred]
> > > Is this considered late binding? If not, what needs changed?
> > >
> > > Thanks!
> > >
> > > Steve
> > >
> > >[/color]
> >
> >[/color]
>
>[/color]

**MacDermott** · Nov 13 '05, 08:22 AM

Re: Late Binding??

So what happens if you remove your reference to the Microsoft Office 10
Library?

"Steve" <nospam@nospam. spam> wrote in message
news:XhLPd.1163 1$oO.4190@newsr ead2.news.atl.e arthlink.net...[color=blue]
> < CommandBar items programmaticall y >>
> You do if you use:
> Dim Cbr As CommandBar
> Dim Ctl As Commandbar.Cont rol
> I have Office97, 2000 and XP installed and only have Microsoft Office10
> Library in my references. Apparently when later versions of Office are
> installed, they remove previous versions of the Microsoft Office Library.
> I'm creating an Access97 application that needs to manipulate a commandbar
> and the controls on the commandbar. That's the reason for all my[/color]
questions.[color=blue]
> The end user of this application will only have MS Office97 installed and
> thus Microsoft Office 8 Library in his references. Since I don't have that
> reference, I went to late binding with:
> Dim Cbr As Object
> Dim Ctl As Object
>
> <<it would still be my guess that this reference (Microsoft Office10
> Library) would not port well to an earlier version of Access.>>
> I think you are very right about this! Upon closer examination, the path[/color]
to[color=blue]
> Microsoft Office10 Library on my computer is:
> C:\Program Files\Common Files\Microsoft Shared\Office 10\mso.dll
> I presume that the path to references is carried with the database for all
> checked references. Therefore, I must assume that the other machine would
> never be able to find the Microsoft Office10 Library (mso.dll) because it[/color]
is[color=blue]
> an Office 8 machine and would not even have an Office 10 folder.
>
> Steve
>
> "MacDermott " <macdermott@nos pam.com> wrote in message
> news:0UKPd.1162 2$oO.5794@newsr ead2.news.atl.e arthlink.net...[color=green]
> > I stand corrected.
> >
> > In some earlier threads, I'd said you needed to use CreateObject in this
> > case.
> > For some reason, I thought that you needed the Office Objects Library to
> > access CommandBar items programmaticall y. I just tried that out and
> > realized I was wrong on that.
> >
> > I've lost track of who the OP was on this -
> > the issue seemed to be running this code on machines using different
> > versions of Access.
> > There was a reference to a specific version of the Office Objects
> > Library; it would still be my guess that this reference would not port[/color]
> well[color=green]
> > to an earlier version of Access.
> > If this reference is not needed for other reasons, it should be[/color]
> removed.[color=green]
> > If it's needed somewhere else, that place is probably where we need[/color][/color]
to[color=blue][color=green]
> > look for the problem.
> >
> > - Turtle
> >
> > "Douglas J. Steele" <NOSPAM_djsteel e@NOSPAM_canada .com> wrote in message
> > news:zMqdnficXr 3o15LfRVn-qg@rogers.com.. .[color=darkred]
> > > Yes, that's late binding.
> > >
> > > --
> > > Doug Steele, Microsoft Access MVP
> > > http://I.Am/DougSteele
> > > (no e-mails, please!)
> > >
> > >
> > >
> > > "PC Datasheet" <nospam@nospam. spam> wrote in message
> > > news:1dAPd.1136 6$oO.1502@newsr ead2.news.atl.e arthlink.net...
> > > >I have this:
> > > > Dim Cbr As Object
> > > > Dim Ctl As Object
> > > > Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
> > > > Set Ctl =
> > > >[/color][/color]
> Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth")[color=green][color=darkred]
> > > > Is this considered late binding? If not, what needs changed?
> > > >
> > > > Thanks!
> > > >
> > > > Steve
> > > >
> > > >
> > >
> > >[/color]
> >
> >[/color]
>
>[/color]

**Steve** · Nov 13 '05, 08:22 AM

Re: Late Binding??

I have removed the reference and am using late binding as:
Dim Cbr As Object
Dim Ctl As Object
Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
Set Ctl =
Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth")
and all works well.

Steve

"MacDermott " <macdermott@nos pam.com> wrote in message
news:vcRPd.1195 1$oO.4254@newsr ead2.news.atl.e arthlink.net...[color=blue]
> So what happens if you remove your reference to the Microsoft Office 10
> Library?
>
> "Steve" <nospam@nospam. spam> wrote in message
> news:XhLPd.1163 1$oO.4190@newsr ead2.news.atl.e arthlink.net...[color=green]
> > < > CommandBar items programmaticall y >>
> > You do if you use:
> > Dim Cbr As CommandBar
> > Dim Ctl As Commandbar.Cont rol
> > I have Office97, 2000 and XP installed and only have Microsoft Office10
> > Library in my references. Apparently when later versions of Office are
> > installed, they remove previous versions of the Microsoft Office[/color][/color]
Library.[color=blue][color=green]
> > I'm creating an Access97 application that needs to manipulate a[/color][/color]
commandbar[color=blue][color=green]
> > and the controls on the commandbar. That's the reason for all my[/color]
> questions.[color=green]
> > The end user of this application will only have MS Office97 installed[/color][/color]
and[color=blue][color=green]
> > thus Microsoft Office 8 Library in his references. Since I don't have[/color][/color]
that[color=blue][color=green]
> > reference, I went to late binding with:
> > Dim Cbr As Object
> > Dim Ctl As Object
> >
> > <<it would still be my guess that this reference (Microsoft Office10
> > Library) would not port well to an earlier version of Access.>>
> > I think you are very right about this! Upon closer examination, the path[/color]
> to[color=green]
> > Microsoft Office10 Library on my computer is:
> > C:\Program Files\Common Files\Microsoft Shared\Office 10\mso.dll
> > I presume that the path to references is carried with the database for[/color][/color]
all[color=blue][color=green]
> > checked references. Therefore, I must assume that the other machine[/color][/color]
would[color=blue][color=green]
> > never be able to find the Microsoft Office10 Library (mso.dll) because[/color][/color]
it[color=blue]
> is[color=green]
> > an Office 8 machine and would not even have an Office 10 folder.
> >
> > Steve
> >
> > "MacDermott " <macdermott@nos pam.com> wrote in message
> > news:0UKPd.1162 2$oO.5794@newsr ead2.news.atl.e arthlink.net...[color=darkred]
> > > I stand corrected.
> > >
> > > In some earlier threads, I'd said you needed to use CreateObject in[/color][/color][/color]
this[color=blue][color=green][color=darkred]
> > > case.
> > > For some reason, I thought that you needed the Office Objects Library[/color][/color][/color]
to[color=blue][color=green][color=darkred]
> > > access CommandBar items programmaticall y. I just tried that out and
> > > realized I was wrong on that.
> > >
> > > I've lost track of who the OP was on this -
> > > the issue seemed to be running this code on machines using[/color][/color][/color]
different[color=blue][color=green][color=darkred]
> > > versions of Access.
> > > There was a reference to a specific version of the Office Objects
> > > Library; it would still be my guess that this reference would not port[/color]
> > well[color=darkred]
> > > to an earlier version of Access.
> > > If this reference is not needed for other reasons, it should be[/color]
> > removed.[color=darkred]
> > > If it's needed somewhere else, that place is probably where we[/color][/color][/color]
need[color=blue]
> to[color=green][color=darkred]
> > > look for the problem.
> > >
> > > - Turtle
> > >
> > > "Douglas J. Steele" <NOSPAM_djsteel e@NOSPAM_canada .com> wrote in[/color][/color][/color]
message[color=blue][color=green][color=darkred]
> > > news:zMqdnficXr 3o15LfRVn-qg@rogers.com.. .
> > > > Yes, that's late binding.
> > > >
> > > > --
> > > > Doug Steele, Microsoft Access MVP
> > > > http://I.Am/DougSteele
> > > > (no e-mails, please!)
> > > >
> > > >
> > > >
> > > > "PC Datasheet" <nospam@nospam. spam> wrote in message
> > > > news:1dAPd.1136 6$oO.1502@newsr ead2.news.atl.e arthlink.net...
> > > > >I have this:
> > > > > Dim Cbr As Object
> > > > > Dim Ctl As Object
> > > > > Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
> > > > > Set Ctl =
> > > > >[/color]
> > Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth")[color=darkred]
> > > > > Is this considered late binding? If not, what needs changed?
> > > > >
> > > > > Thanks!
> > > > >
> > > > > Steve
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >[/color]
> >
> >[/color]
>
>[/color]

**MacDermott** · Nov 13 '05, 08:22 AM

Re: Late Binding??

Even on other versions of Access?

"Steve" <nospam@nospam. spam> wrote in message
news:MvSPd.1256 $SO.93@newsread 3.news.atl.eart hlink.net...[color=blue]
> I have removed the reference and am using late binding as:
> Dim Cbr As Object
> Dim Ctl As Object
> Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
> Set Ctl =
> Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth")
> and all works well.
>
> Steve
>
> "MacDermott " <macdermott@nos pam.com> wrote in message
> news:vcRPd.1195 1$oO.4254@newsr ead2.news.atl.e arthlink.net...[color=green]
> > So what happens if you remove your reference to the Microsoft Office 10
> > Library?
> >
> > "Steve" <nospam@nospam. spam> wrote in message
> > news:XhLPd.1163 1$oO.4190@newsr ead2.news.atl.e arthlink.net...[color=darkred]
> > > < > > CommandBar items programmaticall y >>
> > > You do if you use:
> > > Dim Cbr As CommandBar
> > > Dim Ctl As Commandbar.Cont rol
> > > I have Office97, 2000 and XP installed and only have Microsoft[/color][/color][/color]
Office10[color=blue][color=green][color=darkred]
> > > Library in my references. Apparently when later versions of Office are
> > > installed, they remove previous versions of the Microsoft Office[/color][/color]
> Library.[color=green][color=darkred]
> > > I'm creating an Access97 application that needs to manipulate a[/color][/color]
> commandbar[color=green][color=darkred]
> > > and the controls on the commandbar. That's the reason for all my[/color]
> > questions.[color=darkred]
> > > The end user of this application will only have MS Office97 installed[/color][/color]
> and[color=green][color=darkred]
> > > thus Microsoft Office 8 Library in his references. Since I don't have[/color][/color]
> that[color=green][color=darkred]
> > > reference, I went to late binding with:
> > > Dim Cbr As Object
> > > Dim Ctl As Object
> > >
> > > <<it would still be my guess that this reference (Microsoft Office10
> > > Library) would not port well to an earlier version of Access.>>
> > > I think you are very right about this! Upon closer examination, the[/color][/color][/color]
path[color=blue][color=green]
> > to[color=darkred]
> > > Microsoft Office10 Library on my computer is:
> > > C:\Program Files\Common Files\Microsoft Shared\Office 10\mso.dll
> > > I presume that the path to references is carried with the database for[/color][/color]
> all[color=green][color=darkred]
> > > checked references. Therefore, I must assume that the other machine[/color][/color]
> would[color=green][color=darkred]
> > > never be able to find the Microsoft Office10 Library (mso.dll) because[/color][/color]
> it[color=green]
> > is[color=darkred]
> > > an Office 8 machine and would not even have an Office 10 folder.
> > >
> > > Steve
> > >
> > > "MacDermott " <macdermott@nos pam.com> wrote in message
> > > news:0UKPd.1162 2$oO.5794@newsr ead2.news.atl.e arthlink.net...
> > > > I stand corrected.
> > > >
> > > > In some earlier threads, I'd said you needed to use CreateObject in[/color][/color]
> this[color=green][color=darkred]
> > > > case.
> > > > For some reason, I thought that you needed the Office Objects[/color][/color][/color]
Library[color=blue]
> to[color=green][color=darkred]
> > > > access CommandBar items programmaticall y. I just tried that out and
> > > > realized I was wrong on that.
> > > >
> > > > I've lost track of who the OP was on this -
> > > > the issue seemed to be running this code on machines using[/color][/color]
> different[color=green][color=darkred]
> > > > versions of Access.
> > > > There was a reference to a specific version of the Office[/color][/color][/color]
Objects[color=blue][color=green][color=darkred]
> > > > Library; it would still be my guess that this reference would not[/color][/color][/color]
port[color=blue][color=green][color=darkred]
> > > well
> > > > to an earlier version of Access.
> > > > If this reference is not needed for other reasons, it should be
> > > removed.
> > > > If it's needed somewhere else, that place is probably where we[/color][/color]
> need[color=green]
> > to[color=darkred]
> > > > look for the problem.
> > > >
> > > > - Turtle
> > > >
> > > > "Douglas J. Steele" <NOSPAM_djsteel e@NOSPAM_canada .com> wrote in[/color][/color]
> message[color=green][color=darkred]
> > > > news:zMqdnficXr 3o15LfRVn-qg@rogers.com.. .
> > > > > Yes, that's late binding.
> > > > >
> > > > > --
> > > > > Doug Steele, Microsoft Access MVP
> > > > > http://I.Am/DougSteele
> > > > > (no e-mails, please!)
> > > > >
> > > > >
> > > > >
> > > > > "PC Datasheet" <nospam@nospam. spam> wrote in message
> > > > > news:1dAPd.1136 6$oO.1502@newsr ead2.news.atl.e arthlink.net...
> > > > > >I have this:
> > > > > > Dim Cbr As Object
> > > > > > Dim Ctl As Object
> > > > > > Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
> > > > > > Set Ctl =
> > > > > >
> > >[/color][/color][/color]
Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth")[color=blue][color=green][color=darkred]
> > > > > > Is this considered late binding? If not, what needs changed?
> > > > > >
> > > > > > Thanks!
> > > > > >
> > > > > > Steve
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >[/color]
> >
> >[/color]
>
>[/color]

**Steve** · Nov 13 '05, 08:23 AM

Re: Late Binding??

It works in my Access97 database and I have since tried it in Access2000, XP
as 2000 and XP as 2002 and it also worked in all of them.

Steve

"MacDermott " <macdermott@nos pam.com> wrote in message
news:2KUPd.1221 7$oO.1660@newsr ead2.news.atl.e arthlink.net...[color=blue]
> Even on other versions of Access?
>
> "Steve" <nospam@nospam. spam> wrote in message
> news:MvSPd.1256 $SO.93@newsread 3.news.atl.eart hlink.net...[color=green]
> > I have removed the reference and am using late binding as:
> > Dim Cbr As Object
> > Dim Ctl As Object
> > Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
> > Set Ctl =
> > Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth")
> > and all works well.
> >
> > Steve
> >
> > "MacDermott " <macdermott@nos pam.com> wrote in message
> > news:vcRPd.1195 1$oO.4254@newsr ead2.news.atl.e arthlink.net...[color=darkred]
> > > So what happens if you remove your reference to the Microsoft Office[/color][/color][/color]
10[color=blue][color=green][color=darkred]
> > > Library?
> > >
> > > "Steve" <nospam@nospam. spam> wrote in message
> > > news:XhLPd.1163 1$oO.4190@newsr ead2.news.atl.e arthlink.net...
> > > > < > > > CommandBar items programmaticall y >>
> > > > You do if you use:
> > > > Dim Cbr As CommandBar
> > > > Dim Ctl As Commandbar.Cont rol
> > > > I have Office97, 2000 and XP installed and only have Microsoft[/color][/color]
> Office10[color=green][color=darkred]
> > > > Library in my references. Apparently when later versions of Office[/color][/color][/color]
are[color=blue][color=green][color=darkred]
> > > > installed, they remove previous versions of the Microsoft Office[/color]
> > Library.[color=darkred]
> > > > I'm creating an Access97 application that needs to manipulate a[/color]
> > commandbar[color=darkred]
> > > > and the controls on the commandbar. That's the reason for all my
> > > questions.
> > > > The end user of this application will only have MS Office97[/color][/color][/color]
installed[color=blue][color=green]
> > and[color=darkred]
> > > > thus Microsoft Office 8 Library in his references. Since I don't[/color][/color][/color]
have[color=blue][color=green]
> > that[color=darkred]
> > > > reference, I went to late binding with:
> > > > Dim Cbr As Object
> > > > Dim Ctl As Object
> > > >
> > > > <<it would still be my guess that this reference (Microsoft Office10
> > > > Library) would not port well to an earlier version of Access.>>
> > > > I think you are very right about this! Upon closer examination, the[/color][/color]
> path[color=green][color=darkred]
> > > to
> > > > Microsoft Office10 Library on my computer is:
> > > > C:\Program Files\Common Files\Microsoft Shared\Office 10\mso.dll
> > > > I presume that the path to references is carried with the database[/color][/color][/color]
for[color=blue][color=green]
> > all[color=darkred]
> > > > checked references. Therefore, I must assume that the other machine[/color]
> > would[color=darkred]
> > > > never be able to find the Microsoft Office10 Library (mso.dll)[/color][/color][/color]
because[color=blue][color=green]
> > it[color=darkred]
> > > is
> > > > an Office 8 machine and would not even have an Office 10 folder.
> > > >
> > > > Steve
> > > >
> > > > "MacDermott " <macdermott@nos pam.com> wrote in message
> > > > news:0UKPd.1162 2$oO.5794@newsr ead2.news.atl.e arthlink.net...
> > > > > I stand corrected.
> > > > >
> > > > > In some earlier threads, I'd said you needed to use CreateObject[/color][/color][/color]
in[color=blue][color=green]
> > this[color=darkred]
> > > > > case.
> > > > > For some reason, I thought that you needed the Office Objects[/color][/color]
> Library[color=green]
> > to[color=darkred]
> > > > > access CommandBar items programmaticall y. I just tried that out[/color][/color][/color]
and[color=blue][color=green][color=darkred]
> > > > > realized I was wrong on that.
> > > > >
> > > > > I've lost track of who the OP was on this -
> > > > > the issue seemed to be running this code on machines using[/color]
> > different[color=darkred]
> > > > > versions of Access.
> > > > > There was a reference to a specific version of the Office[/color][/color]
> Objects[color=green][color=darkred]
> > > > > Library; it would still be my guess that this reference would not[/color][/color]
> port[color=green][color=darkred]
> > > > well
> > > > > to an earlier version of Access.
> > > > > If this reference is not needed for other reasons, it should[/color][/color][/color]
be[color=blue][color=green][color=darkred]
> > > > removed.
> > > > > If it's needed somewhere else, that place is probably where we[/color]
> > need[color=darkred]
> > > to
> > > > > look for the problem.
> > > > >
> > > > > - Turtle
> > > > >
> > > > > "Douglas J. Steele" <NOSPAM_djsteel e@NOSPAM_canada .com> wrote in[/color]
> > message[color=darkred]
> > > > > news:zMqdnficXr 3o15LfRVn-qg@rogers.com.. .
> > > > > > Yes, that's late binding.
> > > > > >
> > > > > > --
> > > > > > Doug Steele, Microsoft Access MVP
> > > > > > http://I.Am/DougSteele
> > > > > > (no e-mails, please!)
> > > > > >
> > > > > >
> > > > > >
> > > > > > "PC Datasheet" <nospam@nospam. spam> wrote in message
> > > > > > news:1dAPd.1136 6$oO.1502@newsr ead2.news.atl.e arthlink.net...
> > > > > > >I have this:
> > > > > > > Dim Cbr As Object
> > > > > > > Dim Ctl As Object
> > > > > > > Set Cbr = Application.Com mandbars("Cours eCalendarMonth" )
> > > > > > > Set Ctl =
> > > > > > >
> > > >[/color][/color]
> Application.Com mandbars("Cours eCalendarMonth" ).Controls("Cal endarMonth")[color=green][color=darkred]
> > > > > > > Is this considered late binding? If not, what needs changed?
> > > > > > >
> > > > > > > Thanks!
> > > > > > >
> > > > > > > Steve
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >[/color]
> >
> >[/color]
>
>[/color]

Late Binding??

Late Binding??

Comment

Comment

Comment

Comment

Comment

Comment

Comment