Binding

[dancer]

Using VB.Net and ASP.Net 1.1

I will create a form that will have maybe 20 or 30 fields. Can I bind that
information directly, or does it have to go into a database first?

 

[Masudur]

Using VB.Net and ASP.Net 1.1

I will create a form that will have maybe 20 or 30 fields. Can I bind that
information directly, or does it have to go into a database first?

Hi,

"Can I bind that information directly"...
Bind information where...
where is the data...?
and where you want to bind?

Thanks
Munna
www.kaz.com.bd
http://munnacs.110mb.com

 

[mark4asp]

Using VB.Net and ASP.Net 1.1

I will create a form that will have maybe 20 or 30 fields. Can I bind that
information directly, or does it have to go into a database first?

You can bind it from an XML source or even from literal constansts. For
instance if you put the data into an ArrayList or a List<T> you can bind
that.

But why would you NOT get it from a database?

 

[Mark Rae [MVP]]

Using VB.Net and ASP.Net 1.1

I will create a form that will have maybe 20 or 30 fields. Can I bind
that information directly, or does it have to go into a database first?

As others have said, yes you can, but why make all that extra work for
yourself...?

 

[dancer]

A person will be filling in information on a form.
When I bind from a database, the information appears in columns and rows.
Do I send the information that the person fills in to a database first, and
then retrieve it to have it in colums and rows, or do I bind it from the
variables of the form without going to a database?
Maybe I don't know exactly what binding is. It seemed a simple way to get
info into a grid. ???

 

[dancer]

RE:
As others have said, yes you can, but why make all that extra work for

yourself...?

So what is the most efficient way to get information from a user input form
into a grid?

Thanks

 

[Larry Bud]

RE:
As others have said, yes you can, but why make all that extra work for


So what is the most efficient way to get information from a user input form
into a grid?

Thanks

Obviously you have to store the info somewhere, right? The form gets
bound to the database, then your datagrid gets bound the db as well.

 

[Mark Rae [MVP]]

RE:
As others have said, yes you can, but why make all that extra work for

So what is the most efficient way to get information from a user input
form into a grid?

In order to avoid another lengthy exchange where you tell us a little bit
more information with every subsequent reply, can you please give a summary
of *precisely* what you are trying to achieve here...

It sounds like:

a) you have a data input page with 20 or 30 fields

b) the user will fill in these forms and hit a submit / postback button

c) you then want to display the information which has just been entered in
some sort of tabular structure

Am I right so far?

Do you need to do anything more than that? Does the data entered need to
persist outside this operation? By that, I mean does the user need to be
able to retrieve this information tomorrow...?

Maybe I don't know exactly what binding is. It seemed a simple way to get
info into a grid. ???

You most certainly do not *have* to store data in a database to display it
in a grid...

 

[dancer]

Re:
a) you have a data input page with 20 or 30 fields -CORRECT

b) the user will fill in these forms and hit a submit / postback button -
CORRECT

c) you then want to display the information which has just been entered in
some sort of tabular structure SOMEWHAT CORRECT

I have 2 different projects.
Project #1
I now have a data input page as a) and b) above - except 47 fields. The
results of this form are emailed in html format to 3 people in our company.
It works great and it looks great - they are very happy with it.
Now I need to send this information to a database as well, so that 6 months
or a year or 2 years from now, I can sort the info on whatever field I
choose, make a report and we can analyze the data. The database needs to be
updated each time the person hits submit. I need the database to come to my
computer. There will not be a large number of submissions - 100 - 300 per
year.

Project #2
I will have a data input page as a) and b) above. I also need for it to go
by email to 2 or 3 recipients in the company. But the way I coded Project
#1 was very laborious - a DIM for each field of the form, an html line for
each field to email, an ASP.net control for each field. I wondered if
binding the information would be a better way. (I'm not sure I have a good
handle on what "binding" does.) Or would it be better to send the info to
a database, and then make a report from there.

 

[Mark Rae [MVP]]

Re:
a) you have a data input page with 20 or 30 fields -CORRECT

I have 2 different projects.

LOL! I see - good job I asked, eh...!

Project #1
I now have a data input page as a) and b) above - except 47 fields. The
results of this form are emailed in html format to 3 people in our
company. It works great and it looks great - they are very happy with it.
Now I need to send this information to a database as well, so that 6
months or a year or 2 years from now, I can sort the info on whatever
field I choose, make a report and we can analyze the data. The database
needs to be updated each time the person hits submit.
OK.

I need the database to come to my computer.

I'm going to have to ask you for further clarification on that, I'm
afraid... Principally, could you explain precisely what you (think you) mean
by making a database "come to your computer"...?

Project #2
I will have a data input page as a) and b) above. I also need for it to
go by email to 2 or 3 recipients in the company. But the way I coded
Project #1 was very laborious - a DIM for each field of the form, an html
line for each field to email, an ASP.net control for each field.

Seems fine to me...

I wondered if binding the information would be a better way. (I'm not sure
I have a good handle on what "binding" does.)

I think that may be a large part of the problem... Added to that, IIRC,
you're stuck with ASP.NET 1.1, so a whole slew of functionality is simply
unavailable to you...

Or would it be better to send the info to a database,

Well, you're going to have to store the data in a database anyway in order
to satisfy the requirements for Project #1... Oh, hold on - it *is* the same
data, isn't it...?

and then make a report from there.

Again, you're going to need to define what you mean by "make a report". I'm
sorry to appear to be labouring this, but the other day in a different
thread you wrote: "No, Excel would not create the reports. I would create
the reports using Merge capabilities in Microsoft Word, with a table in
Excel as my data to merge. I don't know how to get the data from the
website to my computer."

This is a *highly* convoluted (and, frankly, ludicrous!) method for creating
reports in ASP.NET. Can you please explain precisely what your reporting
requirements are...?

 

[dancer]

Now I need for YOU to clarify some things.
"Seems fine to me." WHAT seems fine to you?
--------------------------------------------------------------------------
"Well, you're going to have to store the data in a database anyway in order

to satisfy the requirements for Project #1... Oh, hold on - it *is* the
same data, isn't it...?"

Which data are YOU talking about?
Data for Project #2 is different from data for Project #1 The data for
Project # 1, as I explained well, goes now to an email and would also go to
a database.
----------------------------------------------------------------------------------------------------------------
This is a *highly* convoluted (and, frankly, ludicrous!) method for creating

reports in ASP.NET. Can you please explain precisely what your reporting
requirements are...?

So what would YOU suggest? If I already knew the best way, I wouldn't be
writing to this forum.
----------------------------------------------------------------------------------------------------------------------
When you finally get around to giving a suggestion it is VERY GOOD. But we
have to put up with a lot of Condescension, Criticism, and Crankiness to get
it. Why don't you use your energy and excellent mind in sharing your
knowledge instead of giving us the 3rd degree and criticizing. If I
knew as much as you, I'd have your job instead of mine. What seems obvious
to you is NOT obvious to your students.
I have a long way to go. But I have *come* a long way because of patience
and generosity of others.
I look forward to learning from you!!!

 

[Mark Rae [MVP]]

Now I need for YOU to clarify some things.
"Seems fine to me." WHAT seems fine to you?

The method that you are currently using i.e. having a separate TextBox or
other WebControl for each piece of data you wish to capture. This is by far
the simplest (even though you find it 'laborious') method of data capture in
ASP.NET, and by far the most manageable.

Which data are YOU talking about?
Data for Project #2 is different from data for Project #1 The data for
Project # 1, as I explained well, goes now to an email and would also go
to a database.

OK, so we're talking about two completely separate issues...

So what would YOU suggest? If I already knew the best way, I wouldn't be
writing to this forum.

There are many excellent reporting solutions available for ASP.NET. The one
you choose will, of course, depend on your particular requirements...

Firstly, what precisely do you mean by *report*?

Do you mean simply a web page where a set of data has been turned into
meaningful information? If so, then you need do nothing more than display
that web page.

Or, do you mean something which the user can download to their machine in
read-only form and then maybe forward on as necessary? If so, then something
like a PDF would seem to fit the bill. There are several options here - this
is the one I use: http://www.siberix.com. Unfortunately, you are stuck in
ASP.NET v1.1 - there's nothing I can do about that, but it does impose a
fair amount of limitations over what I can suggest for you. E.g.
http://www.gotreportviewer.com - a superb reporting solution for ASP.NET,
but you just can't use it...

Or, do mean something which the user can download to their machine and then
continue to work on? Maybe something like an Excel spreadsheet? If so, then
I would use this: http://www.aspose.com/Products/Aspose.Cells/Default.aspx

When you finally get around to giving a suggestion it is VERY GOOD. But
we have to put up with a lot of Condescension, Criticism, and Crankiness
to get it.

OK, let me turn that on its head. What you interpret as condescension,
criticism and crankiness is simply my attempt at persuading you to explain
precisely what you need! This thread is a case in point. If you look at your
original post, it says:

"Using VB.Net and ASP.Net 1.1
I will create a form that will have maybe 20 or 30 fields. Can I bind that
information directly, or does it have to go into a database first?"

There is no mention of the two separate projects for which you are
apparently looking for the same answer. There is also no mention of the
email requirement. Similarly, there is no mention of any reporting
functionality etc. Can you see how little information you provided there,
yet you expect an all-encompassing answer? I'm glad that you find my
suggestions VERY GOOD, but do you not see how difficult it is to get the
stage where I can actually provide these suggestions?

What seems obvious to you is NOT obvious to your students.

Ah yes but, by the same argument, what seems obvious to you is not obvious
to everybody else!

I look forward to learning from you!!!

And I look forward to helping you!! But please help me to help you!

This may be of some assistance: http://asp.net.do/faq/help.aspx

 

[dancer]

1. I have found that when I include too much detail or more than one problem
at a time, it is too confusing. One simple question at a time seems to get
a better answer from most helpers. Sometime I am looking for a general
direction. Sometime I am looking for a specific answer to a particular
problem.

2. RE: "Or, do mean something which the user can download to their machine
and then

continue to work on? Maybe something like an Excel spreadsheet? If so,
then I would use this:
http://www.aspose.com/Products/Aspose.Cells/Default.aspx"

THIS is what I have been saying. But I don't want to buy a 3rd party
package that may or may not work and puts another possibility for problems
in the mix, as well as a learning curve. SURELY THERE IS A POSSIBILITY.

3. I have asked our hosting service to address the problem of not having
ASP.net 2.0. Meanwhile, I have to work with the limitations. I don't make
the decision of which hosting service to use.

4. I read the Welcome to the ASP.NET FAQ. I quote from there: "Please treat
all participants with respect, valuing divergent views and contrary
opinions.Be polite."

I hope you will continue to share your knowledge. I will try to be more
specific when I can.

Thank you.