I have recently gotten some advice that said "No professional programmer should ever use a FormView in Production". My application is a data entry application. Wouldn't the FormView control be ideal for this type of application?

Thanks

If the FormView control does what you need it to do then by all means use it.

And where did this "advice" come from? I wouldn't take any advice that isn't supplied along with some evidence.


-Peter
compiledthoughts.com

I thought this advice was a little suspect until I read a blog by the author of this book (http://www.amazon.com/ASP-NET-Bluepr...2098305&sr=8-1).

Reading this made me question whether or not I should use the FormView control. Can I assume from your response that in your opinion that there is no problem with using FormView control in a production application?

Do you forsee any problems with using a FormView control for all of my many data entry screens?

Thanks

Where is the blog post and what does it say?

I can't see a problem with using that control where it is appropriate, but I wouldn't as far as declaring that it would be suitable for all your data entry needs as I don't know what those are.

-Peter
compiledthoughts.com

Here is the article that I mentioned that says not to use any of the view controls.

http://professionalaspnet.com/archiv...bout-.NET.aspx

I am curious as to your thoughts on this.

Thanks

I just came across another article that stated the 'DataView' controls are bad. Here is that article.

http://www.realsoftwaredevelopment.c...n-performance/

Sorry to get into your thread... The controls are not "bad", they are not the best thing if your site will have thousands of hits at the same time. Yes, they have overhead and the output is not good. But unless you expect your site to be massive (and that's what they are referring in those blogs) they are not a bad thing...

HTH

Gonzalo

================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
^^Took that from dparsons signature and he Took that from planoie's profile
================================================== =========
My programs achieved a new certification (can you say the same?):
WORKS ON MY MACHINE
http://www.codinghorror.com/blog/archives/000818.html
================================================== =========
I know that CVS was evil, and now i got the proof:
http://worsethanfailure.com/Articles...-Hate-You.aspx
================================================== =========

No problem joining my thread. The more the merrier. My site is an intranet site that will have many pages (at least 200). All of my pages are data entry in nature. There will never be more than 200 users at one time. So, can I assume that using a FormView for each (or most) of these data entry screens is okay?

Since the output of the FormView is not good, are there controls that where the output is better or would I be better off doing everything manually?


Thanks

so, we can asume that you will have no more that a couple of user on each page. And if this site is an intranet site, I don't think you have to worry too much about data transfer or page load (that is minimum, depends on your DB setup)..

I think you will do it more than ok.

HTH

Gonzalo

================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
^^Took that from dparsons signature and he Took that from planoie's profile
================================================== =========
My programs achieved a new certification (can you say the same?):
WORKS ON MY MACHINE
http://www.codinghorror.com/blog/archives/000818.html
================================================== =========
I know that CVS was evil, and now i got the proof:
http://worsethanfailure.com/Articles...-Hate-You.aspx
================================================== =========

Thanks for the help.