Right, I've come across a big problem, but I dont know if it's an ES problem, a VDB problem, or my problem.

Basically, I tried to save a record with a column called "Actioned" (Char 1) with the data '-1'. Obviously that's two characters so the saved failed.

My try/catch caught the exception, so I preceeded to re-fire my code, and I get this exception when trying to load a query:

Error 101 (Provider v. 3.3.1.57): Cannot open data storage or file:  Program Files\iVirtualDocket\Database\iVirtualDocket.vdb3
Error 117 (Provider v. 3.3.1.57): Cannot open database:  Program Files\iVirtualDocket\Database\iVirtualDocket.vdb3

Any ideas how to fix this? Who's problem is it? Here is my code that causes the above error, althrough any collection load has the same issue.

1    
2                m_BreakIns.Query.Where(m_BreakIns.Query.Actioned.Equal("0"));
3                m_BreakIns.Query.Load();

Restarting the application fixes the bug and it's 100% reproduceable.

I have no issues with SQL CE, unfortunately I just seem to have issues with VistaDB at the moment.

Cant wait to get the beta! If you need my database or anything to test, then I can provide it.

The bug is still present, ignore my post in the beta thread.

The error is the same as above (different project). All the DLLs are version 2008.1.831.0.

"Error 117 (Provider v. 3.3.1.57): Cannot open database:  \\Program Files\\Logger\\Database\\#Hidden#.vdb3"

Here is my stack trace:

"at VistaDB.Engine.Internal.DirectConnection.OpenDatabase()          at VistaDB.Engine.Internal.DirectConnection.OpenDatabase()          at VistaDB.Engine.Internal.LocalSQLConnection.OpenDatabase()          at VistaDB.Provider.VistaDBConnection.Open()          at EntitySpaces.Interfaces.esTransactionScope.Enlist()          at EntitySpaces.VistaDBProvider.CF.DataProvider.LoadDataTableForDynamicQuery()          at EntitySpaces.VistaDBProvider.CF.DataProvider.EntitySpaces.Interfaces.IDataProvider.esLoadDataTable()          at EntitySpaces.Interfaces.esDataProvider.esLoadDataTable()          at EntitySpaces.Interfaces.esDynamicQuery.Load()          at EntitySpaces.Core.esEntityCollection.LoadAll()          at #Hidden#.fAssetSelection.LoadAssetTypes()          at #Hidden#.fAssetSelection.Initialise()          at #Hidden#.fMain.GetAssetId()          at #Hidden#.fMain.ShowReview()          at #Hidden#.fMain.btnReview_ImageButtonClicked()          at Tmsss.Pda.Controls.ImageButton.ImageButton.ClickEvent()          at System.Windows.Forms.Control.OnClick()          at System.Windows.Forms.Control.WnProc()          at System.Windows.Forms.Control._InternalWnProc()          at Microsoft.AGL.Forms.EVL.EnterMainLoop()          at System.Windows.Forms.Application.Run()          at #Hidden#.Program.Main()          "

Edit:

From the testing I've done, the only explanation I can think is that you're not closing the connection after an exception in a database command. This means that when I come to reload something after an exception, the application falls over as it cant get exclusivity to the database. The connection property on the connectionstring must be in Exclusive Read or Write mode. Is there any way to force the database close, or do you need to release a new version?

I might be completely wrong, but this app needs to be finished today, so any help is greatly appreciated. Thanks.

Thanks Mike, that's fixed it!

What was it?