Just wanted to mention that we are crashing quite often when using Sesame on our network. There are at least 2 issues we are seeing consistently.

1. When a users is connected to a server and his pc is idle for an extended amount of time(1 hour?), the connection to the server "closes" or gets lost but the form remains open. when trying to advance to a new record or close the record, sesame stops responding and must be closed. Sesame Server thinks the user is still connected (and will not allow him to re-connect)and must be forcefully shut down. This has been noticed while working over an internet connection. We have not tested this problem on a LAN.

2. When a user is working in a form (.db file) and a programmer is saving (possibly loading and previewing) the same form in designer (.dsr file), the user working in the .db file gets kicked out. Occaisionally Sesame on the users machine crashes and must be closed/reopened.

Hopefully these are things that will be addressed soon.

Thanks for the great software!

Steve in Texas

Quote:


There may be some sort of socket "timeout" behavior being enforced by the operating system itself. In addition, the Internet is definitely geared to cut off inactive connections. We may have to create some sort of "heartbeat" behavior, although we would want it to be optional. Otherwise it will sit there chewing up resources for those who don't need it because it's constantly asking "Are you still there?".

Quote:


This is a bit of a red herring. The db and the dsr are not connected in any way. This is like saying that the person typing in one text file gets kicked out because someone is typing in a different text file. You may want to take a closer look at what behavior is causing the problem.

Quote:


Steve,

The db and the dsr are not even the same files. The only time they talk to each other at all is when you first open the db in Designer to turn it into a dsr, and when you Reconcile. Are you absolutely certain that he has the db open and not the dsr? It is possible to open a dsr in Runtime by using the command line.

Erika,

I just checked his screen. He is adding to the .db file. He is not is Designer. (Blue title bar at top of screen shows C:\Sesame\data\appname.DB) Version 1.0.3

He is using Windows 98

Something new....I opened a different form in the .dsr file (also in the same app hes working in ) and saved. He crashed after hitting f10. (Sesame has performed an illegal operation).

Any thoughts?

Steve in Texas

Running more tests as we speak.

Erika,

Thanks for the concern. We both just rebooted and are still having the same problem. Here are the details.

The mouse is used for everything. No keyboard other than the Users press of F10.


I click on an icon with these settings (pasted from icon):

Target:
C:\Sesame\Program\sdesigner.exe -client ntserver:20020:20021

Start in: ""   (blank)

I use mouse to double click on file named RugStudio.DSR

Progress box shows "Loading 0-100%". Sesame opens to tree.

I use mouse to click Forms>Redesign>Rugstudio!Photo Editor. (Same problem happens in at least 1 other form, also)

Photo Editor forms open.

I click "Save Layout Design" (with or without making changes to the form. Doesnt seem to affect problem)

Progress box shows "Saving 0-100%" Then the Progress box shows AGAIN "Saving 0-100%" (should it save twice???) All seems normal on my machine. (At this point User crashes at next record change. For testing, he presed f9 and f10 continuously while I was saving. Crash happens right when the save hits approx 100%)

Here is what the user did:

Double clicks icon with these settings:

Target:
C:\sesame\data\sesame.exe -client NTserver:20020:20021

Start in:
C:\Sesame  

Uses mouse to click File>Open>Rugstudio.DB (.dsr files are not visible)

Progress box shows "Loading 0-100% Flashes very quickly. Tree Opens.

Single click on Search/Update "Photo Editor"

Enter search specs and f10 through the first 10 records just to 'browse'.

All is well with updating until the above mentioned "saved of the .dsr form". The next press of F10 Crashes sesame with message "Sesame has performed an illegal operation and will be shut down".

My machine is using Windows 2000 and the user is using windows 98 with no other programs running. This problem seems to be getting worse. Earlier User was being forced back to the tree with the Sesame splash screen showing, now he is getting the "Illegal operation" box.

I'm going to try this scenario on a non windows 98 box and see what happens. I'll post my results.

Thanks again for your concern.

Steve in Texas.

Update: Recreated the users steps exactly on a windows XP Home machine and left it open in update mode of form Photo Editor.

Went to my computer and just clicked "Save" (Photo editor form was still open from last test)

Went back to XP machine and tried to F10 and after a slight delay and no response (hourglass, pointer, hourglass, pointer, still no response, F10 again) CRASH! (Sesame.exe has encountered a problem and needs to close. We are sorry for the inconvenience. Send error report?)

ps. Server is running on XP Pro and does show the user as disconnected after they close their "crash window". Also, just to confirm, since I know this is hard to beleive. I AM working in the .DSR file, not the .DB file and the users ARE only working in the .DB file. We never even got far enough to reconcile.

Thanks

Steve in Texas

Shall I send you the db and dsr? Total size would be about 9 megs for each.

I could delete some records from the .db and delete all .dsr files and send to you.

Just let me know.

Thanks again for your interest.


Steve in Texas.

Update:

I saved my .dsr file to Temp.DB and opend it on the XP Home machine. Problem still occured but did something a bit different.

After pressing F10 on User machine, Sesame splash screen showed up and Progress box showed "Loading 0-100%). At 97% Crash screen displayed "Sesame.exe has encountered a problem and needs to close...".

Should I re-install Sesame Runtime or just send the files to you to look at?

Steve in Texas