>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.

Nope. Identical ControlSource for the two editboxes. In fact, I used the Thor tool for comparing objects to compare the two editboxes. Other than size and position issues, the only properties that differ are Enabled (.F. where it works, .T. where it doesn't), IntegralHeight (which I failed to set .T. on the editing form), TabIndex and Name (also slightly different for no good reason).

No code in either one.

Backing up for a moment, it did turn out the user had older runtimes. We replaced those and he's still seeing the problem. To make it more interesting, I made a similar change to a second table, that is, turned two CHAR(60) fields into a single memo field. I don't have a display-only case for this one, but instantiating the form class for editing gives the same error "Error instantiating the object EDTNOTES." And, as in the other case, works fine here, but not there.

Things I've already checked:

1) That the data structure changes actually happened. He sent me the two relevant tables after running the update code the other day and the new memo field is there; the old char fields are gone. Since he could find these where expected, I think I can also rule out something related to virtualization.

2) That the code runs correctly on my machine with their data.

3) That he's running the build I think he is.

Right now, I'm sending him a fresh build even though there are no changes JIC something was funky in the build.

Tamar