Cerebrus, I haven't forgotten to reply to you on this matter, but simply have been pulled to other projects during the life of this one. Typical of the programming world, from what I notice.
In any event, I have begun to take your advise on my tool; I've moved everything out of the fvEntry_ItemInserting method and got rid of it altogether. Any custom parameters that I needed were setup as suggested in the dsEntry_Inserting event to eliminate most of the hidden fields. Granted, I still have 3 hidden fields left to get rid of (if I can -- I had a total of 8 since the original post), but it is certainly a good start. I'm still left with the following hiddenfields: hfPrivateOrPublic hfApproved hfMgrNotes I'll be looking into the rest of your suggestions in detail (the dropdownbox included) during the weekend to get rid of more, if possible. Talk to you soon! On Jul 28, 3:14 am, Cerebrus <[email protected]> wrote: > You're welcome, Chuck. I am looking forward to your feedback/comments/ > questions/brickbats etc. ... :P > > On Jul 27, 7:19 pm, Chuck <[email protected]> wrote: > > > > > Cerebrus, > > > I'm certainly going to takeaway quite a bit from your post, as I > > understand a good bit of what you listed. I'll keep you posted and > > what I am able to get done, and will ask questions if needed. > > > A point to bring up on your list though: > > > 1) The user control > > I'm still learning the inner workings of this control, as it wasn't > > originally built by me. It has worked flawlessly for me until I > > decided to get more complex with my code. LOL With that being said, > > I either don't think there is a bindable feature for the control built > > into it. I ideally want to modify the code to add quite a bit more > > stuff to it, as it is a very useful control (or simply learn it > > better). So as a result, some the events of the control (as of this > > post) aren't removable in the code behind without crashing the control > > or modifying the control itself. However, I still can see where I can > > move the private/public out of the Refresh event of the control. > > > Furthermore, I do want to point out that the hfUserID is used for the > > person currently logged into the tool, which traps it by the network > > ID; the user control will not always be populated by the hfUserID > > (think managerial inputs and delegate inputs for other users). > > However, I do have other ways to retrieve login ID's without throwing > > it into a hiddenfield. I'll take your point on that also. > > > I'll keep you posted during the week as to how I come along with your > > suggestions. > > > Thanks a million! > > Charles.- Hide quoted text - > > - Show quoted text -
