Quote:Mark -
I'm delighted that you found a problem because this situation has literally gotten me sick.
With any program, but especially with those that can be configured, programmed, or edited - backup frequently. In 9 out of 10 cases the problem is likely caused by the last thing you did. In this case, the last thing you did was give your image LE an initial value - and that was the cause.
Quote:What I would like to know is whether you know what it is causing.
It was caused by a difference between regular LEs and image LEs. Image LEs have to contact the server individually to get there image contents (the bits and bytes that make the pixels in the image). When a form is cleared (as it is on delete F3), the form contacts the engine to tell it to delete that particular record. Between the time that the form tells the engine to delete that record and the time the engine replies that it has, the form calls "clear()" to set up the initial values of the next form to appear. But if that form has an image, and that image has an initial value, the forms sends another (now nested) command to retrieve the image data. Then the form waits for a reply for its image data request and for a reply for its delete record request. Usually, they will come in in the correct order, but in your app, by chance, the replies come in out of order and the image data goes to the delete record command's reply. This gets the client / server communications out of synch.
Quote:I would feel 1000 percent better if I could talk to someone "live" about this.
Ray will call you tomorrow. I will move it to "top of his in box". In the meantime, back up your application. Set your image's initial value to blank, and see if that has up and running again.