Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1   Report Post  
Posted to microsoft.public.excel.programming
external usenet poster
 
Posts: 3
Default 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




  #2   Report Post  
Posted to microsoft.public.excel.programming
external usenet poster
 
Posts: 11,272
Default Access + Packaging Wizard + Excel

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" wrote in message
...
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






  #3   Report Post  
Posted to microsoft.public.excel.programming
external usenet poster
 
Posts: 3
Default Access + Packaging Wizard + Excel

Hi Bob

Thanks.



"Bob Phillips" escreveu na mensagem
...
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" wrote in message
...
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








  #4   Report Post  
Posted to microsoft.public.excel.programming
external usenet poster
 
Posts: 3
Default Access + Packaging Wizard + Excel

Hi Bob

Thanks.


"Bob Phillips" escreveu na mensagem
...
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" wrote in message
...
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








Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules

Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
Thread Thread Starter Forum Replies Last Post
Excel 2007 Query Wizard problem with Access 2007 extensions Showdad Excel Discussion (Misc queries) 0 December 4th 08 05:57 PM
Packaging Word & Excel files for emailling to preserve links BOBODD Excel Discussion (Misc queries) 1 November 7th 06 08:56 PM
WIZARD ARE YOU READY - UPDATING EXCEL FROM ACCESS IN REAL TIME sal21 Excel Programming 8 November 9th 04 01:53 PM
Is there an add-in or a utility for Excel Packaging? Martyn Excel Programming 6 June 25th 04 06:56 AM
function wizard access violations Janwillem van Dijk Excel Programming 0 February 4th 04 10:39 AM


All times are GMT +1. The time now is 08:03 AM.

Powered by vBulletin® Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright ©2004-2025 ExcelBanter.
The comments are property of their posters.
 

About Us

"It's about Microsoft Excel"