.NET (Core and Framework)

6-Sep-09 21:31

I want something like paper forms that is filled by hand, in my program. The filled form should be stored as a field of type binary in the database. What I need is a framework for making and presenting those forms;for example as a word document...
I want the forms to open without the need for a software(e.g. like word office) . The form should be opened in a .NET windows form and changed there.

Robert_Pan7-Sep-09 2:25

Robert_Pan

7-Sep-09 2:25

VSTO???

Not Active7-Sep-09 2:51

7-Sep-09 2:51

InfoPath ?

only two letters away from being an asset

devboycpp7-Sep-09 3:28

7-Sep-09 3:28

Whatever name . Just a clean solution. I dont want to engage in its complexities.
The font and layout of the form should be fixed and the user would just type in tables' cells and not be permitted to change the layout. No toolbar for changing fonts and the like is needed just typing should be allowed.

If you are a girl ... then ...

Not Active7-Sep-09 3:42

7-Sep-09 3:42

Another option is to use a PDF library to display the form with edit fields. Of course you can alwasy just create your own windows/web form.

You don't need to store the form in a binary format in the database, only the data that was entered.

devboycpp wrote:
Whatever name . Just a clean solution. I dont want to engage in its complexities.

Since we know nothing about your requirements or constraints for the project we can only offer suggestions. It's up to you to determine which is the best method.

only two letters away from being an asset

devboycpp7-Sep-09 4:22

7-Sep-09 4:22

Mark Nischalke wrote:
You don't need to store the form in a binary format in the database, only the data that was entered.

Dude , the reason why I want this is because the fields of the form are many (almost 130 ). The data in fields are all of varchar type. I go crazy having to make a table with 130 fields and a form to show those fields , a stored procedure to update , insert to those fields.

Do you have a more elegant way ?

Not Active7-Sep-09 5:18

7-Sep-09 5:18

Then what happens when the form changes? The previous versions you have stored are all invalid?

A more elegant solution would allow the data to be stored independent of the presentation.
I'm sure this data could also be used for analysis also, forming charts or graphs. It wouldn't be possible in a binary format.

devboycpp wrote:
The data in fields are all of varchar type.

Are the fields truely all varchar, or are you being lazy and making them such? What about validation of the data entered?

If they are all truely varchar then a table could be constructed with a name/value pair. With an identity column, that's only three columns. Is that too much for you?

If they are not all varchar and you need to create a table with seperate columns, using Linq to SQL or Entity Framework you can eliminate the need to write and maitain stored procs. Also, I'm sure there is potenttial to normalize the data and elimiate some of the columns.

Lastly, don't call me dude.

only two letters away from being an asset

devboycpp7-Sep-09 6:52

7-Sep-09 6:52

Mark Nischalke wrote:
Lastly, don't call me dude.

Is it insult to call someone dude or what ?

If you are a girl ... then ...

Not Active7-Sep-09 7:10

7-Sep-09 7:10

To me, yes

only two letters away from being an asset

devboycpp7-Sep-09 7:02

7-Sep-09 7:02

Mark Nischalke wrote:
If they are all truely varchar then a table could be constructed with a name/value pair. With an identity column, that's only three columns. Is that too much for you?

With this solution when creating a form for the first time we have to insert 130 records into the table and when updating likewise. I don't know how much it will affect the performance.

And also when fetching data it is not straightforward to display data in the form.

If you are a girl ... then ...

Not Active7-Sep-09 7:09

7-Sep-09 7:09

devboycpp wrote:
we have to insert 130 records into the table...much it will affect the performance.

You can't be serious? Roll eyes | :rolleyes:

Modern databases, such as SQL Server, can handle thousands of transactions per second. Do you really think 130 rows is going to cripple it?

devboycpp wrote:
And also when fetching data it is not straightforward to display data in the form.

form["field name"] = row["field name"].value

Something like this is too cumbersome for you? OMG | :OMG:

only two letters away from being an asset

devboycpp7-Sep-09 7:23

7-Sep-09 7:23

Mark Nischalke wrote:
form["field name"] = row["field name"].value

For displaying data we need to fetch the records into a DataTable. It will contain 130 records . To display the values for the form fields we need to locate in DataTable to find the desired record matching the form entry. Which is not like you said . The above code is for when all 130 fields are stored in one record of a table.

If you are a girl ... then ...

Not Active7-Sep-09 7:57

Re: Managing paper-like forms in .NET . [modified]

7-Sep-09 7:57

Notice the Something like this statement. Can you use a little imagination or would you like me to write the application for you?

You've gotten all the help you need. I'll expect either a check or a thank you.

only two letters away from being an asset

devboycpp7-Sep-09 8:43

7-Sep-09 8:43

Thanks

Well . I just wanted an elegant way. Seems in this way I should write a function that in its body loops through records of a DataTable and blah blah blah ... like this

string GetFieldValue(string fieldName)
{
    for(int i=0 ; i < table1.Rows.Count ; i++)
    {
         if(table1.Rows[i]["fieldName"].ToString()==fieldName)
         {
               return table1.Rows[i]["Value"].ToString();
         }
    }

    return "";
}

Is it right majesty ? Or you know a more elegant way?

modified on Monday, September 7, 2009 3:33 PM

Not Active7-Sep-09 9:44

7-Sep-09 9:44

This is where Linq to SQL adds elegance to the solution.

Given FormValues is the LinqToSQL representation of your table in which you store the huge array of 130 values.

string value = FormValues.SingleOrDefault(e => e.Name == fieldName);<br />
form[fieldName] = (value == null) ? "Some default" : value;

devboycpp wrote:
Is it right majesty

Don't be an ass

only two letters away from being an asset

devboycpp7-Sep-09 9:59

7-Sep-09 9:59

Mark Nischalke wrote:
Don't be an ass

only two letters away from being an asset Wink | ;)

I thought it is a kind of respect .

devboycpp7-Sep-09 9:35