Okay the Subject line may be a LITTLE misleading, but it's not far off.

I tried to open my application in Designer to create a new .dsr file to work in. I got a message saying I couldn't open it. I was able to open it from the icon (client/server path, etc.). So I backed up the app and named it something else. I am able to open this in Designer. So I deleted the original app and renamed my backup the original app's name - Workorders. When I try to open it with Designer - same message - the dreaded TWO LINE one.

Well, before I renamed the app as Workorders I created a new .dsr file. So I save as a new app from that, Workorders_0909. I can open that up with designer, no problem. So rename my Workorders as Workorders_bad, and my Workorders_0909 as Workorders. Tried to open with Designer - same message.

I've checked for "ghosts" (I'm mapped to the server), couldn't see anything. Double checked how may users were being served - just one, me. I did this because yesterday I was somehow logged on twice after a fatal error blew me off the computer and I had to reboot. Odd that Sesame Server didn't know that I was gone. We rebooted the Server, no problem.

So -- any ideas as to why when I rename ANY of my backups to my original name I can't open it with Designer? Again, I CAN access the app via my icon. I know it's the correct file because I can view the changes and look at the time/date stamp as to when the file was last accessed.

Always on the weekend!
FRed

What's the number for Ghostbusters??

I'm back to the same issue. New info - I entered a new record in my backup file and did a "save as": Workorders. I open Workorders and -- no new record. I deleted the workorders app and tried this again. Same results.

I guess I'll name my backup something new and change everyone's shortcut to point to the new file, but I'd think there'd be an easier way to get back to "normal".

So has anyone successfully gotten rid of a ghost application? After I fired off the program as described above both the Workorders and Workers.dat file reappeared in my list of files in the folder. I tried deleting them, refired the program, same result. I tried renaming them, refired the program, same result. I deleted just the .dat file, refired the program and got a DIFFERENT result - the .dat file was now 509kb vs 1kb. I thought "maybe", but, no - no new "test" record. Then I deleted just the Workorders file. Same result, only reverted back to 1kb. I checked file attributes, nothing set to Read-Only or any other thing checked besides Archive.

I can see I'll have to redirect my shortcuts to my newly named backup, which is fine and all. I'd just like to try to figure this thing out -- and there are a lot smarter people "out there".

Thanks for any insights,
Fred

With or without the popcorn?? LOL

I guess the main question is: How do I rid my server of a "ghost" program?

I can view my old Workorders and Workorders.dat files in the folder on the server. If I delete the files and then try to launch the app from my original shortcut, it actually launches, and the Workorders and Workorder.dat reappear in the folder, with the .dat file showing only 1kb. If I rename the files I can also still launch the app. I know it's not a matter of two different files in two different places because if I add a record when launched from the shortcut and then go to the file in the folder and click on it, the new record is there.

I've renamed my backup and am now working in it as my main app, so this is not a great deal, it's just that there's a ghost in my machine -- and it's "scaring" me.

Thanks Mark - I won't get to this until Friday (I only work weekends). I will, however, have our SysAdmin restart the Server. Thanks again!

Fred

Yes - I understood that  - from the numerous times I've had to have him restart it. I guess I should have said "the Server program" instead of "the Server" or just "Server". I knew what I meant, I just didn't "splain" it very well.

NICEBERG wrote on Sep 11^th, 2006 at 1:18pm:


You can run the sesame executable from a mapped hard drive. You will still need to specify the -client flag when it is invoked. Your users may not like having to wait while the Sesame executable is pulled through the net to their machine, every time they start Sesame.

You may consider mapping the client machines's hard drives onto a single machine and using a simple script on that single machine to update the executables on all of the clients.

Quote:


Here it sounds like you are talking about mapping the Sesame application (the .db and .dat files). If you do this the server alone will execute the application through file sharing, and be slower because it will need to hit the net to get to its files. The client computers have no access to these files except by going through the Sesame server software, and will be unaffected.

If you try to have multiple clients (running standalone, no "-client" flag) attempt to access the same application files (.db and .dat) on a shared harddrive that they all share, the files will locked for all but the first client. If you unlock the files to allow other clients (standalone) to get to these files, you will absolutely damage the files permanently - destroying your data.