ActiveX problems with 3.0.F.2 (fwd)

Question

This is the message I sent to tech support. Has anyone else seen this
type of thing? Any suggestions (even half-baked) would be appreciated.
-- Adam
---------- Forwarded message ----------
Date: Tue, 17 Mar 1998 13:48:17 -0600 (CST)
From: Adam Mckee <[email protected]>
To: [email protected]
Subject: ActiveX problems
Product: Forte
Version of Forte: 3.0.F.2
Server OS: HPUX
Client OS: NT/Win 95
DBMS: Oracle
Reproducible(?): Yes
Brief description of issue:
I have experienced problems using ActiveX controls. I have tried several
controls, including:
o Microsoft Forms 2.0 SpinButton
o Microsoft Forms 2.0 CheckBox
o Microsoft Forms 2.0 EditBox
o AddSoft Gantt/OCX
o Sheridan MonthView
o Sheridan DayView
o Sheridan DateCombo
o Microsoft Calendar Control
(specifically mentioned in a Forte technote)
I have experienced problems with all of these controls. With the Sheridan
DateCombo, the Forte environment crashes when I attempt to drop the
control into a form using the "Insert Control..." button. Before the
environment crashes, I get a series of informational and error dialog
boxes as follows:
o error: unexpected exception -10737415717
o error: The Error Manager stack is empty (repeated 3 times)
o information: the workspace is now read-only because the
repository is disabled.
o error: Exception escaped from terminating task CW.Display
o ERROR: TMgr.Terminate: fatal error terminated partition
With all the other controls I tried, the ActiveX support appears to work
properly until I attempt to bind an instance of the olegen-generated
class to the control itself in the window's Init() method:
--- MyWindowClass.Init() ----
super.Init();
myActiveXControl = new();
After this has been done, the Forte environment may "hang" when I interact
with the control at run-time. For example, each time a generate a mouse
event inside the control, I risk hanging the Forte environment. I might
be able to interact with the control 50 times before the environment
hangs, or it might hang after a single mouse click. Until the crash/hang
occurs, the ActiveX support appears to work properly: I am able to trap
mouse events, and interact with the control using the provided interface.
Any help or advice you can offer would be appreciated. I would be happy
to provide any additional information you may require.
-- Adam McKee

Answer 1

I don’t recall any problems importing to “selected item’ which I always use so I define where it goes and what it’s called.
Do you have Aperture’s Activity Window open so you can see where it is hanging up? Is it just busy generating Previews etc.? I know it sounds more serious than just ‘busy’ but would be interesting to know what it’s doing then.
After these problems, assuming that previews and thumbnails are generated correctly, it may be a good precaution to restart Aperture while holding down the OPTION and COMMAND keys so you can Repair Permissions or Repair the database. Even rebuilding the database is fairly quick if those first two options are ineffective.