(your app) called SysFatalAlert with the message : "Field.c, Line:175,
Invalid isertion point position".
(your app) called SysFatalAlert with the message : "Field.c, Line:2770,
Invalid isertion point position".

Both of these errors can be caused by called FrmCustomAlert if the resulting
error message (after substitution of your passed in strings) ends with a
"\n" char.

I post this for information only, because I just wasted 30 minutes working
this out, and no one seems to have noticed it before.

(Yes, similar errors can be created by passing empty / null as a string
parameters to this function too... )

Alan Ingleby

--
For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/