How to Store Form Data in Memory in windows application using class file

Question

1.00/5 (2 votes)

See more:

.NET3.5

i am creating windows application in which i have two forms employee_details and communication_details.i do not use databse. In Employee details form fill up employee details after that i clicked on next button it goes to communication_details form and fill up employee communication data after that i clicked on saved the data must be saved on memory.i am taking too much variable in class file to store data in memory but which is wrong.

Posted 15-Aug-12 2:43am

Manohar Khillare

Add a Solution

Comments

[no name] 15-Aug-12 9:12am

Okay so? What is it that you expect from us? There is no question stated, vague description of some sort of a problem, no code for what it is that you are trying to do that you are having a problem with.

Aditya Mangipudi 15-Aug-12 10:57am

I am not sure why you are not using a database but if you want to store all the data in the memory (please show some code), you need to create an object each for both forms with all the fields.
public class EmployeeData
{
public int Id {get; set;}
public string EmployeeName {get; set;}
....
}

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)

Sergey Alexandrovich Kryukov · Answer 1 · 2012-08-15T07:47:00

The question is unclear and looks naive. You are trying to find an application-specific approach to a very general problem (but anyway don't provide enough information).

Try to think in the following direction: why would you need to save form data, in memory or not? A form is needed not for itself, it plays a role submissive to the semantic of some application, is used just a UI presentation and control; using the form, the user look at data and express the decisions on how to modify the data.

So, first of all, you need to isolate the data from the UI presentation of it. You need to have some data model which stays in memory (in your case; I'm not analyzing applicability of the memory presentation of it, assuming that you are right here) and can persist in one or another way (not always, but otherwise your application could not create or use any data artifacts). The data model (your employees and there relations, communications) should not depend on the UI. Then, you will need to bind this data with your UI somehow. In a simple case, you should have a method of populating the form(s) with data model and a method for updating the data model according to the state of your UI controls.

You need to review your design and start from here. I would suggest you learn and analyze applicability of the following architectural patterns (http://en.wikipedia.org/wiki/Architectural_pattern_(computer_science)[^]):

MVVM — Model View View Model,
http://en.wikipedia.org/wiki/Model_View_ViewModel[^],

MVC — Model-View-Controller,
http://en.wikipedia.org/wiki/Model-view-controller[^]),

MVA — Model-View-Adapter,
http://en.wikipedia.org/wiki/Model–view–adapter[^],

MVP — Model-View-Presenter,
http://en.wikipedia.org/wiki/Model-view-presenter[^].

Pay attention for the motivation of those architectures. If you understand it, you would be able to create better design ideas.

—SA