If I had hand coded the parameter screens I would have used some kind of modular design, where adding the parameter to one module would have added it to all four (or 25) parameter screens. Some people use Report Painter to start a report, then enhance and/or copy the generated code. Each of my attempts to use this thing has ended in tears. I just can't see how DS HTML Composer is helpful. The only code that you can fairly safely play with is JavaScript you add manually. One of the things I learned is: besides the four or five html and proprietary tags that make up one report parameter, which I made sure the name and id of were exactly the same on each screen, I overlooked the "compUid" which is what I believe to have messed everything up. I never reverted to backups because at each five minute interval I thought I was close to correcting things. It took me three hours to unravel this mess. I've been at the HTML development game for so long and I am usually very careful, so I thought I'd save time by using the GUI on one screen and then copy the updated code to the other three. I had to jam this new one in between other existing ones, meaning I had to nudge the others out of the way. I needed to add a new control for a new parameter to these four screens. I have four report parameter screens designed in HTML Composer. DS HTML Composer: So very, very discouragedIt's taken me two hours to unwind from three frustrated hours of undoing a mess I created in DS HTML Composer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |