[quote=345776:@Greg O’Lone]My statement about multiuser was one of experience, not documentation, but as soon as the guys get together for today’s meeting, I’ll try to get a definitive answer.
As for more ideas, from your statements, it sounds like you’re getting some sort of program corruption when it crashes, but I find that extremely hard to believe as I’ve never seen this happen with a web app before.
Are you sure that the whole app needs to be replaced? Could it be that just the database is corrupt?
Just out of curiosity, when you get into this state, you might want to try opening that database file with another app to see if that’s possible… that might confirm the data corruption. If it opens and you can operate on it, it may just be a locking issue.
Another possibility… when assigning the folderitem to the database, you might check the following conditions:
0. Folderitem.Parent.IsWritable =True
0. FolderItem.IsWritable =True
0. FolderItem.IsReadable = True[/quote]
Well so far if it was a DB corruption normally the new compiled app will not be able to open the database and to see the data, so far once i put the new compiled app it works smooth, so i still have no clue why it happens that one but still under process of debugging that .
Now to come back to our title , it seems that the session gets killed only after the browser closes so there is no way for me to actually close properly the database unless i tell all the users to close their window which is hard as some of them might not be in the office or in front of the pc but they let their interface on.
So is it very hard for me to properly close the database .
What i did was, creating a custom class with a timer super and putting there the code to kill the sessions and to close the db but for some reasons does not work .
So when i press a button in the admin , Maintenance on, it fires the timer.
Here is the code :
[code]If App.MaintenanceMode Then
If IsRunning = False Then
IsRunning = True
For i As Integer = 0 To App.SessionCount-1
debugModule.Log(“tmrST - Username : " + App.SessionAtIndex(i).Cookies.Value(“username”) + " was online.”)
App.SessionAtIndex(i).MsgBox("We are shutting down now.")
If App.SessionCount = 0 Then
debugModule.Log("tmrST - Not more sessions, should Quit")
IsRunning = False
debugModule.Log("tmrST - There are still " + App.SessionCount.ToText + " sessions active.")
So in the debugging once is killing all the sessions still have the browser page opened, once this is closed manually then the app finally gets closed and the db gets cleaned up.
One issue that i noticed is that on MAC it works smooth after all the tests while on windows it does not close the db at all some times so something hangs there.
I will check as well what you suggested and see what i get.
Any update on the multi user location ?