I'm getting the following after a design change.

This application has been unlocked while running.
This application will no longer save changes to the application files.
It is recommended you close this application at once.

Then Sesame Locks up, Have to shut it down using task manager. 

Quote:

Was the DB file loaded on the Sesame Server when you did the Reconcile?

-Ray

proudpoppy wrote on Sep 28^th, 2007 at 4:26pm:

I had the same thing happen tonight.

I suspect it was because the application that I was reconciling (App1) had been the target of an XLU for another Sesame session running a different app (App2). App2 was still open when I reconciled App1.

They were both being run standalone, but I'm thinking that App2 still had App1 open in memory, similar to how Sesame Server will retain apps in an "open" condition if they were used for an XLU. Does that sound possible, Ray?

Erika,

I was more asking if that was why I had that error message.

I was looking through records in search/update mode when the power problem happened, I don't know what the other user was doing at the time, we both tried to load the appl back but the message came up it was locked, after unlocking the application we used it without incident until dinner time when I shutdown the server and made the security change and reconciled, when I loaded the application in Sesame it got to 99% and then the message came up and it locked up. I only have one Sesame server running, I deleted the db & dat files and saved as a new application, going to make some more changes today and do another reconcile, I hope it goes o.k. We have "skips" in the power almost daily and I felt the problem happened at that time, I'll see about getting a new ups next week and fix it so a foot won't cut it off, I  remember having a utility in QA and paradox to fix similiar problems and was wondering if Sesame could use one?

Made design changes and reconciled over the weekend, and so far no problems this morning, no power blimps this morning so far. 

Quote:


Hello Carl,

I just now saw your post, and Yes that is more than likely what you had happened. Sesame Standalone is pretty much just the Server and the Client rolled into one so it will behave pretty close to the same when it comes to file loading and X commands.

-Ray

Edited:


Hello Erika

Thanks for the reply.  Prevention is better than cure!!    

Don  

If you are getting this problem, it's one of two things. It means that the files have either been unlocked since they were first opened by this Server or standalone copy of Sesame or the files were read-only when opened and Sesame could not set the locked flag.

I would recommend making a backup, then shutting down the Sesame Server, restarting it and opening the file from one client. Make a note of any errors that come up when opening the files. Open a form, retrieve a record and pres F10. You should not get this error message. If you do, double check any batch files you may have that unlock files or anything of that sort.

-Ray