Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Applications / Excel / July 2008



Tip: Looking for answers? Try searching our database.

XLM macro dialog.box command

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
KevinJustie - 18 Jun 2008 22:36 GMT
I have a bunch of Excel 4 XLM macros, and was thrilled to discover that they
still work in Excel 2008, except... I can't get the dialog.box command to
work -- crashes the program ("Excel has encountered a problem and needs to
close").    I thought it might be because I wasn't specifying size/location
(first row of dialog box definition table is blank in most of them), but
putting in some values didn't help; still crashes.  Happens in Leopard and
Tiger, but it has always worked fine under all previous versions of Excel.
Anyone else encountered this, or have any explanation/solution/workaround?

thanks!

kevin
Fergal Condron - 19 Jun 2008 20:38 GMT
Hi Kevin,

Could you give an example of the XLM code you are using and the crash log
from the Microsoft Error Reporting Tool by clicking on the More Information
button when it crashes?

This would be great in trying to narrow this down!

Many thanks,
Fergal.

Signature

Fergal Condron,
Macintosh Business Unit
Microsoft Corp.
This posting is provided ³AS IS² with no warranties, and confers no
rights.

>I have a bunch of Excel 4 XLM macros, and was thrilled to discover that
>they
[quoted text clipped - 10 lines]
>
> kevin
KevinJustie - 19 Jun 2008 21:25 GMT
>Could you give an example of the XLM code you are using and the crash log

Here's a chunk of the macro:

=SELECT("startdate2")
=CLEAR()
=DIALOG.BOX(dateselectiondialog)
=RETURN()

I tried another worksheet that has a macro with a bunch of dialog boxes, and
the first 3 or 4 worked OK, but then it hits one that kills it, just as in
the case of the one above.  In this second worksheet, the dialog boxes that
do work are all very simple:  just text with an OK button, or a single list
of options in a list box, plus an OK button.  The one that kills it, on the
other hand, has roughly 20 text labels and input fields.  So that kind of
makes a little sense, but as you can see below, the dateselectiondailog is
also very simple, and that kills it, too, so....?

And here's the "dateselectiondialog" table

    61    60    395    151       
5    9    13            Enter the first date you want sheets printed for (m/d/yy):   
8    41    45    171           
1    145    96    64        OK   

And from the log (I assume you didn't want the long list of loaded modules,
but I have it it you need it):

Error Signature:
Exception: EXC_BAD_ACCESS
Date/Time: 2008-06-19 15:09:58 -0500
Application Name: Microsoft Excel
Application Bundle ID: com.microsoft.Excel
Application Signature: XCEL
Application Version: 12.1.0.080409
Crashed Module Name: Microsoft Excel
Crashed Module Version: 12.1.0.080409
Crashed Module Offset: 0x00652aa1
Blame Module Name: Microsoft Excel
Blame Module Version: 12.1.0.080409
Blame Module Offset: 0x00652aa1
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409

Thread 0 crashed:

#  1  0x00653aa1 in __mh_execute_header + 0x00652AA1 (Microsoft Excel +
0x00652aa1)
#  2  0x00508f81 in __mh_execute_header + 0x00507F81 (Microsoft Excel +
0x00507f81)
#  3  0x00603b44 in __mh_execute_header + 0x00602B44 (Microsoft Excel +
0x00602b44)
#  4  0x00604208 in __mh_execute_header + 0x00603208 (Microsoft Excel +
0x00603208)
#  5  0x0050c9f7 in __mh_execute_header + 0x0050B9F7 (Microsoft Excel +
0x0050b9f7)
#  6  0x0024d01d in __mh_execute_header + 0x0024C01D (Microsoft Excel +
0x0024c01d)
#  7  0x0024e542 in __mh_execute_header + 0x0024D542 (Microsoft Excel +
0x0024d542)
#  8  0x00118545 in __mh_execute_header + 0x00117545 (Microsoft Excel +
0x00117545)
#  9  0x0011132e in __mh_execute_header + 0x0011032E (Microsoft Excel +
0x0011032e)
# 10  0x0018b928 in __mh_execute_header + 0x0018A928 (Microsoft Excel +
0x0018a928)
# 11  0x0018025e in __mh_execute_header + 0x0017F25E (Microsoft Excel +
0x0017f25e)
# 12  0x0019e0a9 in __mh_execute_header + 0x0019D0A9 (Microsoft Excel +
0x0019d0a9)
# 13  0x0019e207 in __mh_execute_header + 0x0019D207 (Microsoft Excel +
0x0019d207)
# 14  0x001a43ec in __mh_execute_header + 0x001A33EC (Microsoft Excel +
0x001a33ec)
# 15  0x0018025e in __mh_execute_header + 0x0017F25E (Microsoft Excel +
0x0017f25e)
# 16  0x005aeb58 in __mh_execute_header + 0x005ADB58 (Microsoft Excel +
0x005adb58)
# 17  0x96c608e7 in _gHelpers + 0x96C2F507 (AE + 0x000108e7)
# 18  0x0149200a in _McpBrushApply + 0x000030B4 (MicrosoftComponentPlugin +
0x0003400a)
# 19  0x91166763 in .objc_class_name_IPMDFontRange + 0x90E3CB43 (HIToolbox +
0x00007763)
# 20  0x91165b9d in .objc_class_name_IPMDFontRange + 0x90E3BF7D (HIToolbox +
0x00006b9d)
# 21  0x911824ee in .objc_class_name_IPMDFontRange + 0x90E588CE (HIToolbox +
0x000234ee)
# 22  0x01491a8c in _McpBrushApply + 0x00002B36 (MicrosoftComponentPlugin +
0x00033a8c)
# 23  0x96c52648 in _gHelpers + 0x96C21268 (AE + 0x00002648)
# 24  0x96c5257e in _gHelpers + 0x96C2119E (AE + 0x0000257e)
# 25  0x96c52425 in _gHelpers + 0x96C21045 (AE + 0x00002425)
# 26  0x9119147d in .objc_class_name_IPMDFontRange + 0x90E6785D (HIToolbox +
0x0003247d)
# 27  0x005adcaf in __mh_execute_header + 0x005ACCAF (Microsoft Excel +
0x005accaf)
# 28  0x00858e5f in __mh_execute_header + 0x00857E5F (Microsoft Excel +
0x00857e5f)
# 29  0x0051dc59 in __mh_execute_header + 0x0051CC59 (Microsoft Excel +
0x0051cc59)
# 30  0x008913e6 in __mh_execute_header + 0x008903E6 (Microsoft Excel +
0x008903e6)
# 31  0x00891cfb in __mh_execute_header + 0x00890CFB (Microsoft Excel +
0x00890cfb)
# 32  0x008902c2 in __mh_execute_header + 0x0088F2C2 (Microsoft Excel +
0x0088f2c2)
# 33  0x000026ae in __mh_execute_header + 0x000016AE (Microsoft Excel +
0x000016ae)
# 34  0x000025d5 in __mh_execute_header + 0x000015D5 (Microsoft Excel +
0x000015d5)

X86 Thread State:
eax: 0x00000000  ebx: 0x00000040  ecx: 0x00000000  edx:0x00000001
edi: 0x00000003  esi: 0x00508f60  ebp: 0xbfff3608  esp:0xbfff35f0
 ss: 0x0000001f  eip: 0x00653aa1   cs: 0x00000017   ds:0x0000001f
 es: 0x0000001f   fs: 0x00000000   gs: 0x00000037  eflags:0x00010286

Thread 1:

#  1  0x94d435c6 in _signgam + 0x94BA3D86 (libSystem.B.dylib + 0x000015c6)
#  2  0x94dcc29b in _signgam + 0x94C2CA5B (libSystem.B.dylib + 0x0008a29b)
#  3  0x020efd7d in _MerpCreateSession + 0x00000B07 (merp + 0x00002d7d)
#  4  0x020ef3e5 in _MerpCreateSession + 0x0000016F (merp + 0x000023e5)
#  5  0x020ef46c in _MerpCreateSession + 0x000001F6 (merp + 0x0000246c)
#  6  0x020eff25 in _MerpCreateSession + 0x00000CAF (merp + 0x00002f25)
#  7  0x94d746f5 in _signgam + 0x94BD4EB5 (libSystem.B.dylib + 0x000326f5)
#  8  0x94d745b2 in _signgam + 0x94BD4D72 (libSystem.B.dylib + 0x000325b2)

X86 Thread State:
eax: 0xffffffa6  ebx: 0x94dbb0bf  ecx: 0xb00a0a5c  edx:0x94d435c6
edi: 0x0002cc2b  esi: 0xed6ac8d0  ebp: 0xb00a0ac8  esp:0xb00a0a5c
 ss: 0x0000001f  eip: 0x94d435c6   cs: 0x00000007   ds:0x0000001f
 es: 0x0000001f   fs: 0x0000001f   gs: 0x00000037  eflags:0x00000206

Thread 2:

#  1  0x94d4a68e in _signgam + 0x94BAAE4E (libSystem.B.dylib + 0x0000868e)
#  2  0x94d7536d in _signgam + 0x94BD5B2D (libSystem.B.dylib + 0x0003336d)
#  3  0x97151460 in __CMProfileID + 0x9707E33C (ColorSync + 0x00033460)
#  4  0x97163d92 in __CMProfileID + 0x97090C6E (ColorSync + 0x00045d92)
#  5  0x94d746f5 in _signgam + 0x94BD4EB5 (libSystem.B.dylib + 0x000326f5)
#  6  0x94d745b2 in _signgam + 0x94BD4D72 (libSystem.B.dylib + 0x000325b2)

X86 Thread State:
eax: 0x0000014e  ebx: 0x94d7538d  ecx: 0xb0122e7c  edx:0x94d4a68e
edi: 0x0485b9a4  esi: 0xb0123000  ebp: 0xb0122ef8  esp:0xb0122e7c
 ss: 0x0000001f  eip: 0x94d4a68e   cs: 0x00000007   ds:0x0000001f
 es: 0x0000001f   fs: 0x0000001f   gs: 0x00000037  eflags:0x00000246

Thanks for your help!

kevin
KevinJustie - 30 Jun 2008 14:24 GMT
Hi Fergal,

Any resolution coming on this, or have you given up on trying to figure it
out?

thanks

kevin
Fergal Condron - 30 Jun 2008 19:18 GMT
Hi Kevin,

Sorry I was out on vacation and didn't get a real chance of looking into
this.
I'll take a look today and see what's going on.

Many thanks!

Fergal Condron,
Macintosh Business Unit
Microsoft Corp.
This posting is provided ³AS IS² with no warranties, and confers no rights.

On 6/30/08 6:24 AM, in article 8672edc618b26@uwe, "KevinJustie via
MacKB.com" <u44312@uwe> wrote:

> Hi Fergal,
>
[quoted text clipped - 4 lines]
>
> kevin
KevinJustie - 30 Jun 2008 19:58 GMT
> I was out on vacation

Good for you!!

I wasn't trying to nag or rush you, just wondering if it had been forgotten,
since your first reply had come so quickly.
I will patiently await your response!  :-)

kevin
Fergal Condron - 01 Jul 2008 05:50 GMT
Hey Kevin,

I've taken a look at the Macro and so far it is not crashing for me, is
there any way that you can send me a sample file so I can investigate
further?

If so, can you send it to fercon@microsoft.com

Many thanks and again apologies for the delayed response!

Fergal Condron,
Macintosh Business Unit
Microsoft Corp.
This posting is provided ³AS IS² with no warranties, and confers no rights.

On 6/30/08 11:58 AM, in article 8675d8a218ab4@uwe, "KevinJustie via
MacKB.com" <u44312@uwe> wrote:

>> I was out on vacation
>
[quoted text clipped - 5 lines]
>
> kevin

Fergal Condron,
Macintosh Business Unit
Microsoft Corp.
This posting is provided ³AS IS² with no warranties, and confers no rights.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.