EntitySpaces always closes and opens a connection on each call to the database however, connection pooling handles this seamlessly. We have not changed any of the code that deals with connections. I wonder if this is a 3.5 bug? I will do some google research. Can you come up with a scenario that reproduces this. Our support for SQL CE has always worked this way (in fact it does on all of our providers).

---

EntitySpaces | Twitter | BLOG | Please honor our Software License

Read above 1st ...

Can you check your exceptions "Inner Exception" there should be a low level exception in there.

---

EntitySpaces | Twitter | BLOG | Please honor our Software License

See Mike's posts above.

Is this the regular EntitySpaces SqlCe provider, or the CF version?

Do you have a "File Mode" parameter in your connection string?

Our NUnit tests do not use mock objects. We do acceptance/functional tests all the way through to all our supported databases. The SqlCe tests read and write to number of test databases dozens of times without locking up.

I just connected to one of our SqlCe databases in my WinForm test app, loaded a DataGridView, then made several adds, edits, deletes and clicked Save. Then, made several more changes and clicked Save again. All changes were saved, identity keys brought back, and no exceptions thrown.

We should be opening and closing connections with each Load and Save, and not holding any connection open. As a single user database, I believe it can have multiple connections open for foreground and background operations, but there is no connection pooling. That stack trace looks pretty intense. Can you reproduce this in a simpler app against Northwind?

---

David Neal Parsons
www.entityspaces.net

I will try to repro in a simple app. I am useing the Full Framework 3.5 not CF. I will look into the inner exception right now. Give me just a little while and I will try to repro against NorthWind.sdf or simple sdf and send to support.  Thanks,

William

The Inner Exception is "Nothing" I am building small app to try and repro right now

Sorry I am unable to repro it outside of the application I am working on. I feel it is a problem in my code. You are completly correct that ES is not locking the DB file. The provider works as it should. So it is my error I will have to track down. Thank you for your replies and your information.

I was able to repro it in a very simple winform. It only happens when I am using an Image field. I will send a Test Solution to the support email. And if you guys would take a look at it I would greatly appriciate it.

I feel really dumb. The problem I am seeing has nothing to do with ES 2008 nor SQL Ce nor Images Fields. I apologize for bothering you guys with a rookie mistake. The errors appeared at the same time that I updated the ES Rubtimes to the release veersion so I just assumed the problem was with ES. But ES is working very good. I am recieving the error becuase in my connection string I am using a relative path to the DB file. This is fine until I open a Open File Dialog becuase the app no longer starts looking in the app directory but insteads starts looking in the last directory selected with the open file dialog. Therefore the DB file cannot be found. So thank you for time and efforts and sorry that I did not troubleshoot my issue more before posting.

However I do have a question on the RowVersion Field. How do I retrieve it when I update a record or insert a record ? Thanks

Excellent, glad it's all working. As far as the RowVersion after you Save it "should just be there", look in your Entity after calling save and see if it's there, it should be.

---

EntitySpaces | Twitter | BLOG | Please honor our Software License

Thanks