Has the second form possibly got the wrong controlsource specified? If your test environment has 2 memo fields defined your form will work. When the client has only one memo field defined, the second editbox will fail to find it.

>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.
>
>I gave the client a separate EXE to make the database change and he ran it before testing the updated application. The fact that the first form opens correctly and shows the data correctly means the table was properly updated.
>
>I had the client send me the updated table and tested with it here and both forms work as expected.
>
>The only differences I can think of are:
>
>- the client is using Windows 10, while I'm on Windows 7 (but that he could send me the modified table means we're not dealing with virtualization);
>
>- the client has the data living on a mapped drive on a server, while I'm testing locally. Given that things are working generally, I don't see how this could matter.
>
>I'm at a loss. Any ideas?
>
>Tamar