What are you storing in the Hidden fields ? Is it something that is only available on the client side and your hidden fields are the bridge between the client and the server ?
I wouldn't consider 3-6 hidden fields too many, but by the sound of it, you should not require any hidden fields unless you are doing some sort of custom UI interaction via Javascript. Keep in mind that SqlDataSources can accept many different types of parameters. If you can post a simplified code sample for us to try out, I can try to come up with an alternate way to handle this. On Jul 16, 12:16 am, Chuck <[email protected]> wrote: > I have a relatively simple question aside from a major application I'm > building at work. > > Is there such a thing as having too many hidden fields on an ASP.net > page? I currently have 3 now, and may need to pass at least 3 more > back to my sqldatasource. > > Just for a little bit of background to what I'm doing: I only ask > this as I'm currently using a formview (which, on the > insertItemTemplate, has many controls, including an in-house user > control) with a sqldatasource attached to it. This formview will be > used to enter a request for paid time off, and also will be used for > managerial personnel to approve / deny (will be done on the > ItemTemplate or EditTemplate). The sqldatasource (to my knowledge) > won't pickup the parameters within the formview, unless I tie it to a > hidden field (about 3-4 more - depending on how I do my approve / deny > options) and do some code-behind tweaking. > > Hopefully, I'm not being too vague with my question. My issue (from > what I see) isn't my formview at the moment, as I can set up > everything as is. However, if there is a way to pass values > dynamically without programmatically casting items in the code behind > and sending them through hiddenfields, I'm all ears also. Any > clarification would be appreciated.
