A97 runtime app behaves differently on 2 win XP boxes...

[MLH]

Today, I installed an A97 runtime app I built in a hurry this morning.
I took it to a customer who had 3 machines, all running windows
XP. On one machine, an activeX calendar control would NOT
display. OK, so maybe it needed to be registered first. But on that
same machine, I kept getting "Automation errors" citing that some
expression may not result in the name of a macro, user-defined FN,
or [event procedure] - why?

On the second machine, the same app, its procedures and expressions
ran w/o incident. The errors appeared to be untrapped - at least I
didn't recognize any of my error-handling procedures at work whilst
being bombarded with errors. What are automation errors anyway?

The errors are occurring in pretty blahzee routines too - things like
MouseDown events that look like this...

Private Sub MotorNum_MouseDown(Button As Integer, Shift As Integer, X
As Single, Y As Single)
On Error GoTo ErrorMotorNum_MouseDown
Dim ThisForm As String
ThisForm = Me.Name

Dim Help As String, MyControl As Control
Set MyControl = Screen.ActiveControl
Help = MyControl.Tag
If Shift = 0 Then
If Button = RIGHT_BUTTON Then MsgBox Help, 64, MyApp$ & ",
rev. " & MY_VERSION$
Else
If Button = RIGHT_BUTTON Then
Select Case Shift
Case SHIFT_MASK
MsgBox "You pressed SHIFT & Rite Mouse Button!"
Case CTRL_MASK
'MsgBox "You pressed CTRL & Rite Mouse Button!"
Dim PlayHelp As Variant
PlayHelp =
fPlayStuff("C:\TowPack\help\Help0000.wav", 0)
Case ALT_MASK
MsgBox "You pressed ALT & Rite Mouse Button!"
End Select
End If
End If

ExitMotorNum_MouseDown:
Exit Sub

ErrorMotorNum_MouseDown:
Dim r As String, k As String, Message3 As String
r = "The following unexpected error occurred in Sub
MotorNum_MouseDown, CBF on " & ThisForm & "."
k = CRLF & CRLF & Str$(Err) & ": " & Quote & Error$ & Quote
Message3 = r & k
MsgBox Message3, 48, "Unexpected Error - " & MyApp$ & ", rev. " &
MY_VERSION$
Resume ExitMotorNum_MouseDown

End Sub

And OnGotFocus and OnLostFocus expressions that look like these...

=Change2Green("Forms![frmCustEntryfrmVehicleEntryForm]![MotorNum]
OnGotFocus event procedure")
=Change2Gray("Forms![frmVehicleEntryForm]![MotorNum] OnLostFocus event
procedure")

And OnClick event procedures like this...

Private Sub StartTime_Click()
Me!StartTime = GetTheTime()

End Sub
The real heck of it is, the app will work on one XP box but not
another? That confuses me. I tested it on a box running WIN98
and have similar error. I can understand that maybe there are
some significant differences between XP and WIN98. I cannot
understand the OS differences being that significant between
one installation of XP and another - I did notice that the machine
exhibiting the problem was running the SP2 patch. I did NOT
notice whether the machine that worked had the patch or not.
I assume that it did. It was a low-tech office environment and
I imagine that the ladies operating the equipment clicked 'YES'
to everything that was ever presented to them.

This is a real problem for me, and I don't have a clue where to
start debugging.

[MLH]

Well, I'm certainly not a guru, but I know if something's
fixed or broke. I just ran the following DOS command
in a COMMAND prompt on a WIN98 machine after
making sure MSCAL.OCX was in the \windoze\system32
directory...

regsvr32.exe \windows\system\mscal.ocx

Now my automation errors seem to have disappeared?
The code/expressions/etc on the tabbable/clickable
controls running OnClick, OnGotFocus, OnLostFocus,
etc seems to be running fine. And, of course, the
calendar displays and works fine.

Still, do I have a clue you ask? No way, Jose. Anyone
else know what was going on and why registering the
OCX control fixed the other (seemingly unrelated) probs?

[Steve Jorgensen]

On Thu, 16 Jun 2005 22:33:08 -0400, MLH <CR**@NorthState.net> wrote:

Well, I'm certainly not a guru, but I know if something's
fixed or broke. I just ran the following DOS command
in a COMMAND prompt on a WIN98 machine after
making sure MSCAL.OCX was in the \windoze\system32
directory...

regsvr32.exe \windows\system\mscal.ocx

Now my automation errors seem to have disappeared?
The code/expressions/etc on the tabbable/clickable
controls running OnClick, OnGotFocus, OnLostFocus,
etc seems to be running fine. And, of course, the
calendar displays and works fine.

Still, do I have a clue you ask? No way, Jose. Anyone
else know what was going on and why registering the
OCX control fixed the other (seemingly unrelated) probs?

No, but I've seen it before several times.

It appears that once in a blue moon, an install script somehow fails to
register a control on some particular machine even though it does so just fine
on others. The fix is just what you discovered - to manually register the
library. Niether Installshield nor Wise Installer is immune to this problem,
FWICS.

[MLH]

Bummer.