Access + Packaging Wizard + Excel

Access + Packaging Wizard + Excel

This is the scenario:
1. A Contol System being developed through Access 2000.
2. The System controls Excel files using VBA (the "MS Excel 9.0 Obect
Library" box is checked in Tools-References ).
3. Users will run the System trhough LAN.
4. Users's computers have Office 2000, Office XP or Office 2003.

The Problem:
When a computer running Office XP uses the System, an Error occurs on VBA
code when using Excel objects: the Library is not reconized.

How to solve this problem ?
WIll the Packaging Wizard (Access Runtime) get the Excel OLB files and
install in the computers?
Is there any problem to use the Wizard in Office 2000 and later to use the
System in Office XP/2003?
Is it enough to copy the OLB file to the users's computers?

Any other suggestion (or solution) ?


Thanks in advance.

Joe

Sounds like another version mis-match.

You could try late-binding. There is a page describing a technique for this
at http://www.xldynamic.com/source/xld.EarlyLate.html. The example uses
Outlook, but the principle holds.

--

HTH

RP
(remove nothere from the email address if mailing direct)


"Bob" <[email protected]> wrote in message
news:[email protected]...
> Access + Packaging Wizard + Excel
>
> This is the scenario:
> 1. A Contol System being developed through Access 2000.
> 2. The System controls Excel files using VBA (the "MS Excel 9.0 Obect
> Library" box is checked in Tools-References ).
> 3. Users will run the System trhough LAN.
> 4. Users's computers have Office 2000, Office XP or Office 2003.
>
> The Problem:
> When a computer running Office XP uses the System, an Error occurs on VBA
> code when using Excel objects: the Library is not reconized.
>
> How to solve this problem ?
> WIll the Packaging Wizard (Access Runtime) get the Excel OLB files and
> install in the computers?
> Is there any problem to use the Wizard in Office 2000 and later to use the
> System in Office XP/2003?
> Is it enough to copy the OLB file to the users's computers?
>
> Any other suggestion (or solution) ?
>
>
> Thanks in advance.
>
> Joe
>
>
>
>

Hi Bob

Thanks.



"Bob Phillips" <[email protected]> escreveu na mensagem
news:[email protected]...
> Sounds like another version mis-match.
>
> You could try late-binding. There is a page describing a technique for
this
> at http://www.xldynamic.com/source/xld.EarlyLate.html. The example uses
> Outlook, but the principle holds.
>
> --
>
> HTH
>
> RP
> (remove nothere from the email address if mailing direct)
>
>
> "Bob" <[email protected]> wrote in message
> news:[email protected]...
> > Access + Packaging Wizard + Excel
> >
> > This is the scenario:
> > 1. A Contol System being developed through Access 2000.
> > 2. The System controls Excel files using VBA (the "MS Excel 9.0 Obect
> > Library" box is checked in Tools-References ).
> > 3. Users will run the System trhough LAN.
> > 4. Users's computers have Office 2000, Office XP or Office 2003.
> >
> > The Problem:
> > When a computer running Office XP uses the System, an Error occurs on
VBA
> > code when using Excel objects: the Library is not reconized.
> >
> > How to solve this problem ?
> > WIll the Packaging Wizard (Access Runtime) get the Excel OLB files and
> > install in the computers?
> > Is there any problem to use the Wizard in Office 2000 and later to use
the
> > System in Office XP/2003?
> > Is it enough to copy the OLB file to the users's computers?
> >
> > Any other suggestion (or solution) ?
> >
> >
> > Thanks in advance.
> >
> > Joe
> >
> >
> >
> >
>
>

Hi Bob

Thanks.


"Bob Phillips" <[email protected]> escreveu na mensagem
news:[email protected]...
> Sounds like another version mis-match.
>
> You could try late-binding. There is a page describing a technique for
this
> at http://www.xldynamic.com/source/xld.EarlyLate.html. The example uses
> Outlook, but the principle holds.
>
> --
>
> HTH
>
> RP
> (remove nothere from the email address if mailing direct)
>
>
> "Bob" <[email protected]> wrote in message
> news:[email protected]...
> > Access + Packaging Wizard + Excel
> >
> > This is the scenario:
> > 1. A Contol System being developed through Access 2000.
> > 2. The System controls Excel files using VBA (the "MS Excel 9.0 Obect
> > Library" box is checked in Tools-References ).
> > 3. Users will run the System trhough LAN.
> > 4. Users's computers have Office 2000, Office XP or Office 2003.
> >
> > The Problem:
> > When a computer running Office XP uses the System, an Error occurs on
VBA
> > code when using Excel objects: the Library is not reconized.
> >
> > How to solve this problem ?
> > WIll the Packaging Wizard (Access Runtime) get the Excel OLB files and
> > install in the computers?
> > Is there any problem to use the Wizard in Office 2000 and later to use
the
> > System in Office XP/2003?
> > Is it enough to copy the OLB file to the users's computers?
> >
> > Any other suggestion (or solution) ?
> >
> >
> > Thanks in advance.
> >
> > Joe
> >
> >
> >
> >
>
>