If your app was not properly closed, it may think that it is still open by Sesame. It just needs to be unlocked. See page 465 of the Sesame User Guide for instructions on using the sunlock utility.

You can also use the Sesame Server Administration dialog, instructions on page 423-424.

Sunlock.exe is a utility executable. You can run it from a command line. If you have the default Windows install, sunlock.exe can be found at C:\Sesame\Utilities\Lantica\sunlock.exe

You have to run it from a command line. You can't just double-click on it in Explorer becuase it needs an argument (the application to unlock).

From a command line:

c:\sesame\utilities\lantica\sunlock.exe c:\sesame\data\myapp.db

Quote:


Leezerd,

Unfortunately I break my application a lot because I am always messing with it to improve it. I find that it is convenient to add a shortcut Icon that runs Sunlock specifically for my application. There should be no reason to rename your app.

Just create a shortcut and in the target put the path of the sunlock utility and the path and name of your application.

In mine for example my target reads
C:\Sesame\Util\sunlock.exe c:\Sesame\data\myapp.db

This says my utility is on the c drive in my Sesame directory in a sub directory called Util and the utility is named sunlock.exe

it then says the file to run the utility on is

located on the c drive in my Sesame directory in a sub directory called data and the database is called myapp.db.

Capital letters shouldn't be a problem. Use double quotes on the command line to manage the spaces.

sunlock "My Database.db"

Steve,

Restarting the server and sunlocking an app are not related. Using sunlock on an app that is actually loaded by a server is a very very bad thing to do.

Sunlock operates on the flag that tells Sesame that the app is loaded by a server. If you sunlock a loaded app, you allow a second server to load the app, which is a very fast way to destroy your app.

Sunlock is how you tell an app that it is not actually loaded by a server, even though it believes it is. Never sunlock a loaded app.

The above is also why the server can't automatically unlock the app. It doesn't know that the app isn't really loaded by a server. Only you, as a human, know that.

Also, sunlock is an extremely simple program. It always works, unless the file does not exist, which it does tell you. We've been a bit baffled by your statements that sunlock never works for you. Of course, if you're sunlocking loaded applications, that may explain it. 

A locked app and a crashed server are not the same thing.

If you get a message that you can't open your app, the first question is Why not?

There are two likely answers:
1. I just crashed.
2. The app is already loaded by a server or a standalone copy of Sesame.

If you did not just crash, then it is likely to be #2. Also, if you didn't crash, then there is no reason to shut down the server. Having a locked app is not a reason to shut down a server. The Server Interface that shows on the server machine lists the apps that are open. See if your app is on the list before unlocking it. Make sure than no one has the app open standalone.

If you use Emergency Shutdown to kill the Server, then any loaded apps will definitely be locked.

If you are working remotely, then sunlock.exe is the one to use.

If this is happening regularly, you may not have the configuration you think you have. You may have more than one server running. You may (in your self-described panic) be starting a second server when there is one already running with your app happily loaded. You may be unlocking the wrong copy of your app.

You are working remotely with a number of copies of your app scattered around various machines. You may want to take a look at how you work and make sure that you are organized in such a way that you can be sure what servers are running where and using which files.

Also, if you are "crashing all over the place", please let us know. We've looked at your prior posts. The last crash you mentioned was almost a month ago on trying to sort an empty StringArray. The rest of your recent posts have to do with change requests and help with SBasic. A couple of people have sent us crashes lately, but they were both due to the person creating an endless loop in SBasic, a condition that we can't prevent.

Quote:


According to the thread on the subject, using ForceRedraw() solved that issue for you. Is that not working now?

Quote:

Yes, that is one of the very few limitations of Preview mode, although it doesn't crash. It's also not a bug. Just one of the few things that Preview cannot support.

Quote:

If you happen to have unbound elements, yes. That is fixed in the next release.

Quote:

What's wrong with your PopulateComboBoxes button? I see several threads on the subject. The only one involving a crash involved sorting a non-existent StringArray. Is there something else crashing on this?


Quote:

Of course. We're very much looking forward to meeting you!