Wrox Programmer Forums
Go Back   Wrox Programmer Forums > Microsoft Office > Excel VBA > Excel VBA
|
Excel VBA Discuss using VBA for Excel programming.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Excel VBA section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
 
Old July 7th, 2003, 03:28 AM
Registered User
 
Join Date: Jul 2003
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default elusive XLA security problem in Japanese excel 2k

hi guys!

We have developed an Excel Add-in, which works in English and Japanese Excel 2000 on Japanese Windows OS.

However, when we deployed this to the client(which uses a Japanese Excel 2000 on Japanese w2k os) , the XLA wouldn't work. The funny thing is that, the button that we have built with the add-in appeared on the toolbar without much trouble but when the button was click to fire a function that was embedded in the XLA, it wouldn't work as if nothing happened. Worse, no errors appear at all.

Another strange thing is that the said XLA was installed on three different machines in the same company and generated the same results. The macro security set in the excel application was set to medium, which should show a dialogue box that would ask the user if he/she wants to enable or disable macros. BUT, if the button in the XLA worked already, thus, the macro should be able to run the code that is embedded in the XLA also.

Please help, we are so stumped.

Thanks!

 
Old July 8th, 2003, 07:40 AM
Authorized User
 
Join Date: Jun 2003
Posts: 23
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Check the simplest things first, and work your way up.

First, check the button - is there a "macro" assigned to it? Does this macro match the name of the function you are trying to launch in your Add-In?

Next, launch VBA. Is the Add-In there? Is all the code there that you expect?

If all that works, place a breakpoint early in the Add-In code, and attempt to run the Add-In again. Was the breakpoint hit? If so, continue tracing through the code to see if it goes down a path you weren't expecting.

I know that this sounds like "make sure it's plugged in" (which, I guess, it is), but from my experience with creating and deploying XLA's, it is usually the simple things that bite you.

Hope this helps.





Similar Threads
Thread Thread Starter Forum Replies Last Post
Runtime Access 2K and Sql 2K laure Access 0 April 3rd, 2006 08:32 AM
setting security for Access 2K Loralee Access 0 June 19th, 2005 02:39 PM
Copying Multiple Rows in MS Excel 2K using VB .Net Azhar Akbari Excel VBA 2 January 27th, 2005 10:04 AM
XLA files cutovoi Excel VBA 0 January 22nd, 2004 11:39 AM





Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.