aha - the reworded error message was enough to set me in the right direction.. 
i'm switching back and forth several times between window #1 and #2 to display info, 
and the revised error message is enough to make me suspect that i must be altering
the edit field while in the wrong window - i now have a path to track my bug - thx! 

also, your work-around with the EditFields.c worked perfectly.. it lets me work 
until i track my window bug.  muchos garcias once again for all you do. 

jp


| > * Invalid Edit field in FBEditDollarStatement() 
| > * Check button values used with Edit$ function
| 
| The wording of this runtime error message is misleading. In the next release it has been corrected 
| to read: "Invalid id in edit$ statement. Either there is no output window, or the window does not 
| contain an edit field with id xxxx". 
| 
| Your program must be doing
| edit$( xxxx ) = "some text"
| when xxxx is invalid for the reasons given in the new message.
| 
| If you can't track your bug down, here's a workaround for the intrusive alert.
| 
| In FB_5_4_5_Package/build_goodies/EditFields.c, locate the line: 
| FBfullStop( "\pInvalid Edit field in FBEditDollarStatement()", "\pCheck button 
|     values used with Edit$ function", true );
| and delete it, then save the file. 
| Robert P.