Well today was strange. For the last few days the electrical power at work has been just strange. It must be some sort of voltage drop - not really long enough to cause a computer to drop, but long enough for all of the UPSs to alarm. It seems to happen much more in the mornings than the afternoons. Between 7:00 and 10:00 a.m. we had UPSs alarming every few minutes.

Ray and I finally got fed up and turned off the alarms and called the power company. They sent a guy out (surprisingly) and he took a look around. I don't know what he could see just walking around the building....

Also, Ray, came in to a dead computer. His main email box (a pretty critical chunk of hardware) wouldn't boot. Not from HD, or CD, or even floppy. So he popped the HDs and put them in a different computer and rescued his most important files (your emails). So we're down one computer. It was getting pretty old (P3, 128 Mb).

I think, after a while the beeping ruined Ray's mood, so he shuffled his stack of minor outstanding bugs and offered me my choice of bugs to fix. I picked a PrintToHtml bug that I've been meaning to get to. He grabbed a SelectTreeItem bug that has been lingering.

Erika reports that the classes in Toronto went well. She is now getting ready to teach the classes in Dallas.

Lets see if I can address these one at a time:

1. The On Entry bug has been fixed (same day it was found). The fix is available on request.
2. The Sendmail bug is also fixed (also the same day), and available on request.
3. Notes on this are available on the "Sesame Workarounds" page under Support: http://lantica.com/Support/sesame_workarounds.html
4. The table view problem is actually much more specific than simply having a table. As far as we can tell, it requires that the user click in the table, and without clicking or navigating out of the table, or entering edit mode on the table, click in the LE in question. It does not happen from table edit mode, nor from any other LE.
5. Users with subforms, nevermind table view subforms, are definitely in the minority. The majority of Sesame databases are flat.
6. Very few forms have data critical code in a LE on entry event, and those that do, should redesign immediately. This is true with or without the fix (or in 1.1.2). There is no way to be sure that the user will ever navigate to any particular LE. As such, the huge majority of LE on entry programs are (and should  be) convenience functions. If you have data critical code in a LE enter event, it is absolutely necessary that that data be checked on form exit, in that you have no way of knowing if the user simply skipped that LE. This is true for any program that supports both the mouse and multiple fields on a form.

Quote:


Note that I said "data critical". For example, programming that allows selection from a popup - yet still allows the user to enter any value, even if it does not appear in the popup, would not be "data critical" in that any value is legal. It is merely a convenience. But code that checks that a part number is new and has not been used previously, is "data critical".

Quote:


The only "workaround" suggested on the web site is to request the HF from technical support. The workaround you are referring to was a suggestion to the particular customer that discovered this problem and the suggestion was directed to his specific circumstances.

Quote:


It is in 1.1.3 HF1, as stated on the web page.

Quote:


As I mentioned it is available on request for those that need it.

Quote:


Again, if you have data critical code in a LE on entry event - redesign. You have no way of knowing that it will ever run in that the user may (and always can, in any program with a mouse) opt to skip that field.

I agree that support is second to none. 

It must be me.

I cannot find reference to hot fix for this problem.   I see the hot fix for the email problem that I can probably wait for.

From the work arounds page: Quote:

It appears that the hot fix 1.1.3 HF1 is only for the email problem.  If it is for both, then I think the web page should be modified to show the hot fix for each of the items. 

From proudpoppy's response above, it does sound like that patch is for both.  If it is for both, then I will get it and install it.

Thanks Mark.....

I must have missed that instruction too.

I have requested the hotfix.  Could not have done it without you!

Sorry to have you holding my hand with this.......I will try to do better.