With the 3.5 debug ROMs, I'm now getting "Insertion Point
Problem" messages routinely. Never have seen this with other
ROM images.
The problem even occurs within window displayed with
FrmCustomAlert () on top of a screen with entry fields.
What specific event is this message recording? Whatever is
happening seems benign, but presents me with an ugly message.
.....................................
I previously posed the question what API's should you not call
before FrmDrawForm()? (Apart from the obvious ones to
specifically write to the screen, such as CtlDrawControl())
Three I've found so far are as follows:
CtlShowControl
CtlHideControl
FldSetFont
These functions aren't smart enough to know not to draw to the
screen when they shouldn't and hence provoke a "Bus Error" with
the 3.5 debug ROMs.
However FrmShowObject seems to be smart enough not to draw
to the screen when it shouldn't.
The workaround for all three is to directly modify the appropriate
element in the controlling structure, but I'd rather make an API call
than directly write to the field or control structure.
There are probably more....
Roger Stringer
Marietta Systems
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
