Form causing Application to unexpectedally quitWalt Nelson (3/26/14 9:47AM)
Arnaud de Montard (3/26/14 5:35PM)
Walt Nelson (3/26/14 9:47 AM)
Also, consider upgrading to v13.4, the current version of v13.
I would second Arnaud's suggestion of starting the form from scratch.
Duplicating a form will simply copy over any corruption that might
If you want to be systematic, you could start with a new form and copy
selected objects from the offending form to see which object was
causing the crash.
Walt Nelson (Seattle)
New stuff coming!
On Mar 26, 2014, at 9:16 AM, Petsche, Joseph <jpetsche@...
color><param>00000,0000,DDEE/param>II've run across a problem with
v13.3. ?I've been running v13.1 however after the upgrade one
particular dialog box is giving me trouble. If I comment it out, the
Arnaud de Montard (3/26/14 5:35 PM)
Le 26 mars 2014 ý 17:16, Petsche, Joseph a Ècrit :
color><param>00000,0000,DDEE/param>II then duplicated the form into
Better to create a new form, as it seems not to be a complicated one.
Duplicate may have no effect if the form embeds a corrupted object.
Arnaud de Montard
Reply to this message
Summary created 3/26/14 at 4:52PM by Intellex Corporation
Comments welcome at: firstname.lastname@example.org