Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
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
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
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
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
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
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
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 |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Excel 2007 Query Wizard problem with Access 2007 extensions | Excel Discussion (Misc queries) | |||
Packaging Word & Excel files for emailling to preserve links | Excel Discussion (Misc queries) | |||
WIZARD ARE YOU READY - UPDATING EXCEL FROM ACCESS IN REAL TIME | Excel Programming | |||
Is there an add-in or a utility for Excel Packaging? | Excel Programming | |||
function wizard access violations | Excel Programming |