Thank you for the provided screenshots. Without having detailed information about your project, I can imagine, that the behavior belongs to the OpenAccessContext. It looks like that you either don't call the SaveChanges() Method of the Context, which will result in saving all changes to the context and setting the state of the object to hollow(Details about object states can be found here) or you don't create a new OpenAccessContext whenever you are requesting the data. In general it is recommended to have a stateless OpenAccessContext meaning that you are using a using block for the OpenAccessContext whenever you are accessing data. What you can do is the following:
1. Ensure that the changes are indeed pushed to the database. You can do so by simply doing a query in the database itself and checking if the edited values made it there.
2. Request the object in your second application from the server again using its ID. This should act as a refresh and it should fix your problem.
Additionally I would like to point you to our SDK where you can find sample projects for using Telerik OpenAccess ORM in Silverlight environments.
I hope this information is helpful for you.
the Telerik team
Thank you for being the most amazing .NET community! Your unfailing support is what helps us charge forward!
We'd appreciate your vote for Telerik in this year's SQL Server Community Awards. We are competing in TWO categories and every vote counts! VOTE for Telerik NOW >>