>>>Running into something weird. In an inherited application, I just changed a table to have a single memo field instead of two char fields for notes, and replaced the pair of textboxes on the relevant forms with an editbox. There are two forms involved. The first is pretty much display-only, shows a grid of all records on one page and detail of the currently selected record on a second. A button on that form instantiates a form class for editing the record.
>>>
>>>When I test here, all works as expected. Both forms open and show the right data. At the client site, the display form is fine, but instantiation of the editing form class fails with error 1736 and the message says "Error instantiating the object EDTNOTES." That's, of course, the newly added editbox that replaced the two character fields.
>>
>>Solved and embarrassed. Turns out the problem was that the code I wrote to create the memo field used the wrong field name (mNote rather than mNotes) and everything else followed from that. Still a few mysteries from my POV about why some things worked, but this clearly the root cause. (Also an interesting lesson about whether to follow one one's standards or the ones in the inherited app. I also call such fields mNotes, but the fields being replaced were Note and Note2.)
>>
>>Tamar
>
>Hi Tamar,
>
>do you have code to reproduce that? I still do noz understand why this ends uo in Error 1736
>

I think the key piece is that the second form was a form class being instantiated by CreateObject() rather than run with DO FORM.

Tamar