Re: Implementing late binding for VBA

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Bob Phillips (bob.phillips_at_notheretiscali.co.uk)
Date: 01/29/05 

Date: Sat, 29 Jan 2005 01:03:01 -0000

VanS,

Hate to say it, but I think you have gotten in to a real mess by not taking
the advice that Tom and I gave you (sorry to keep dragging your name in Tom,
but it gives extra credence to my statements, I hope <g>). I may be wrong,
but I don't think you would have had this problem if you developed on the
earlier version, and deployed to the later.

As to the specific question asked, I am not ware as to how you can late bind
Office. Excel is an Office application, and as such, even if Excel is
installed stand-alone, the office components are installed, included the
type library. The best I can suggest is that you go to Tools>References and
see if any items are marked as missing, if so correct them. 

-- 
HTH
RP
(remove nothere from the email address if mailing direct)
"VanS" <VanS@discussions.microsoft.com> wrote in message
news:3AD6CD98-B07E-4164-9475-2DCF4E682E97@microsoft.com...
> Hello,
> I have a VB, Excel/Word VBA app running in Excel with automation. I have
> developed it on my Win XP Pro, OFfice 2003 system, but need to make it
> backward compatible to a Win 98 Office 97 platform. After researching it
> seemed best to implement via late binding which I did by removing
references
> to Word which helped that issue. Then I had issues with losing references
to
> the VBA 5.3 Extensibility library and KB articles suggested using late
> binding for that as well, so I removed that reference. Now my app (again
> under Win 98 Office 97 VPC) bombs out unable to use String functions as
Left,
> Mid and Format which are under the VBA Object library. I tried removing
the
> VBA reference but it wouldn't allow me since it was in use. Since Office
97
> uses the VB5 model, I'm assuming I need to do late binding for that as
well.
> Can anyone tell me if that is the case and how to implement it? Or if it
is
> another issue?
> Thanks, God bless,
> Van

Relevant Pages

  • Re: .NET automation version problem
    ... by using early binding and pointing to the references ... But for a pc with word 2003, it shouldn't have the word dll for word2000, so ... I am not familiar with C#, but since we are dealing with COM early binding in both cases, I see no reason why things should be any different. ... The Word VBA Help files are therefore more likely to be meaningful and the code samples easier to adapt when needed. ...
    (microsoft.public.office.developer.automation)
  • Re: Help locating Object Libraries
    ... likely that the typelib can be found when a GetObject or CreateObject ... Late binding allows you to omit the Reference, ... If the VBA References ...
    (microsoft.public.excel.programming)
  • Implementing late binding for VBA
    ... Excel/Word VBA app running in Excel with automation. ... Then I had issues with losing references to ... binding for that as well, ...
    (microsoft.public.excel.programming)
  • Implementing late binding for VBA
    ... Excel/Word VBA app running in Excel with automation. ... Then I had issues with losing references to ... binding for that as well, ...
    (microsoft.public.office.developer.vba)
  • Re: Error or Unexpected Behavior with Office Automation when you use early binding
    ... Tom, how do I invoke late binding? ... >Finding all the references to fully qualify can be ...
    (microsoft.public.excel.programming)