Having trouble with updated data displaying correctly. [Solved]

Question

4.00/5 (1 vote)

See more:

Hello,

I'm having some trouble with getting my forms to display the recently updated data. The weird thing is that this only happens on decimal, int, or other fields having to do with only numbers.

What happens is after the user makes whatever changes they need to make and then saves the new data it'll update it to the database, but the forms will still display the old data, until the application is completely shut down and then re-started. I know the database is being updated exactly like it should be, but the application just won't show the new changes and as I've already mentioned, this only happens with numeric fields. All other data in the application will be shown exactly how it should as long as its not a numeric data type.

One thing I have noticed is that the forms will show the correct data, if I declare it as a new form and then open it compared to just typing in the name of the form with .showdialog. The only problem with this is that, due to the nature of some of the forms in my project, declaring them as a new form would conflict with a nice amount of my code that is already in place.

My question is, what could possibly be causing something like this and what do I need to do to fix it?

Also, my code is written in Visual Basic, and I use LINQ to Entities for retrieving, updating, and deleting records. The database is stored in SQL Server 2008 R2.

Thanks for any and all help.

Posted 11-Oct-12 8:33am

Mr.McCloud

Updated 29-Oct-12 7:31am

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

fjdiewornncalwe · Accepted Answer · 2012-10-11T09:10:00

Solution 1

Whenever you are populating your forms, you should create a new repository context for the given entities so that the data is updated. If you have a static context you may not be seeing the changes if they are saved under another context.

Posted 11-Oct-12 9:10am

fjdiewornncalwe

Comments

Mr.McCloud 11-Oct-12 15:16pm

Hmmm...do you mean like:
"Dim Context as DataAccessLayer.Entities = New DataAccessLayer.Entities" ?

This is how I declare my context in every form. Except of course, with the actual names of the entities and such.

fjdiewornncalwe 11-Oct-12 15:20pm

Yes. I wouldn't use a static variable for the life of the form, but rather an instance for each update so that the instance goes and gets the updated data. That is why it works when you close the form and create a new one.

Mr.McCloud 11-Oct-12 15:21pm

Hmmm, I think I'm getting it. Do you mean then that instead of declaring it at the top, I should declare it in the actual procedure its being called in?

By the way, thanks for the help so far.

fjdiewornncalwe 11-Oct-12 15:26pm

Absolutely. That way it is only alive for the scope in which it is required.

Mr.McCloud 11-Oct-12 15:27pm

Alright, I've tried it and it works perfectly. Thanks for the help. Much appreciated.

fjdiewornncalwe 11-Oct-12 15:29pm

You are very welcome.