At 1:37 PM -0700 4/12/99, David Mottern wrote:
>"ScrDriverNew.c, Line:499, Invalid Params"
>
>Does anyone know what might be causing this?
It's in the code that draws bitmaps. Beyond that, it could be any of
several things, and only stepping through the code will really tell you.
The most likely cause is that it's trying to draw a compressed bitmap with
invalid data, or drawing a bitmap with incorrect copression flags.
If your alert has form bitmaps in it, you might check to see if they're
being correctly generated. Otherwise, it could be coming from the 'saved
bits' bitmap that is being restored when the alert closes. Exactly when
during FrmAlert does this occur? If it's when the alert opens, it's
probably a bitmap in the form, and if it's when the alert is dismissed,
it's probably the saved bitmap.
--Bob
