I just sent you an email on the subject. Before you do anything else, copy the .db and the .dat file to a safe directory. Do this outside of Sesame (using explorer or command line).

I cannot diagnose this over the phone - like Ray. I am not technical support. Without seeing the application I wouldn't even know what questions to ask you. As I mentioned in my email, you can send me your application via email, and I will take a look at it. If at all possible, please include instructions to cause the effect.

Ray will be back in the office on Tuesday.

I have it, but so far don't see anything wrong with it. Can you give me a hint?

Spencer,

So far, the file structure appears to be fine. There is no sign of corruption. If there is something wrong, it is likely to be a pretty easy fix.

I know that you have been up all night (working on the initial value for images). But I don't think you need to worry. This appears to be a "whole" application. Take some time off and get some sleep.

I'll keep looking at it to see if I can find anything wrong. If I don't, I'll pass it on to Ray.

In any case, turn off your computer (maybe a reboot will help) and get some sleep.

Spencer,

I found the problem. It is not severe. It has to do with using an image as an initial value. Until we can get a hot fix release out for this, simply remove the initial value on the image LE.  The problem it was causing is purely one of communications, so your database integrity appears to be fine.

If you absolutely must have an image initial value before the HF release, place a static image where the image LE appears (slightly smaller) and hide the static image when the image LE has a value.

Quote:

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:

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:

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.

Quote:

Something else may be going on in addition to the problem described above.
Quote:


Send the .db and .dat file and a description of the missing records. Please include in  the description informaton that should appear in several of the text fields - as unique as possible.

Did you notice the change after a reconcile? If so, what changes were you putting in with SDesigner? Were these newly entered records, or records that have been in the application for some time? How did you test for whether they were missing?  Were you using a particular search spec to find them?

Just got off the phone with Spencer and figuring out what has happened.

The Initial Value for the image element was messing with communications as Mark stated above. Now while F3 did not appear to delete the current record, it was indeed deleting that record. So if F3 was pressed a couple of times in a row, it would delete a record each time that you pressed F3, it just would not update the screen. Hence the cause of the missing records.

If you notice that F3 is not working for you, and you do not have NotifyForm(4) turned on, do not press it multiple times.

-Ray

Hi -

Well I spent the entire day yesterday and last night trying to identify and replace missing records.

At least as far as the reunion is concerned, I now have all of the appropriate records in place and have been able to input new information. 

I was not able to identify any additional missing records; however, that is not to say that there aren't any.  But, I am certain that it would not be a major problem.  As with everying else in life, nothing is perfect - so what the heck!  lol

I do have a question about the Image Layout Element now that I have removed it from the initial value spec.

Do you think it is safe to use an "if/then" statement to add an image value?  For example, IF someone is attending the reunion AND the image path is blank, THEN I want to insert Need Photo.jpg. 

Thanks!

Ray -

I just added the if/then statement and it works like a charm.  For my particular needs, this is probably a better solution than an initial image value, anyhow.  Too bad that I hadn't thought of using that, in the first place.  lol