 |
|||||
|
As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only. Join the TIBCO Community
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community. | |||||
Read-Only TopicGo | Search | Notify | Tools |
| Edittext vs GUI | Login/Join |
| Platinum Member |
kimo, it honestly depends on what changes you make. If the "text changes" you make to a fex are still supported by the GUI, then you will still be able to open it in the GUI. We quite frequently go between the report painter and the text editor when working with a report. I'm sure there are a lot of different examples, and maybe someone else has a better answer for what types of things you can and cannot do. But the short answer is that what you're hearing is not incorrect, but it's not an "all or nothing" case either. Basically, it depends.  Production: 7.6.6 WF Server <=> 7.6.6 WF Client <=> 7.6.6 Dev Studio Testing: <none> Using MRE & BID. Connected to MS SQL Server 2005 Output Types: HTML, Excel, PDF | |||
|
| <kimo> |
[QUOTE] Thank You Trav | ||
|
| Expert |
Kimo, Trav has it on the nail. Basically, you'll know when you reach the point where the GUI can't handle your coding. T
| |||||||||
|
| <kimo> |
Thank You Tony I guess I'll just have to make sure I keep back ups | ||
|
| Member |
This problem mainly occures when you add code at the beginning of the text editor, before the GUI programming runs. For example, if you create your own dropdown box in the text editor with charactor strings that run first. | |||
|
| Member |
TO avoid this problem, hard code your report and design it in report painter, then go back and create optional charactor strings. | |||
|
| <kimo> |
Thank You Tim, another question was brought up that dialog manager commands thjrows the GUI off too is this the case ? | ||
|
| Platinum Member |
If you put DM commands within the report code itself, then generally yes. Specifically between the "TABLE FILE" and "END" commands of a report. But, keep in mind that the DM actually has a "GUI" portion to it too if you're doing IFs and GOTOs etc. But if you simply build DM commands into other parts of the fex, then it doesn't necessarily "break" the GUI portion of any preceeding or subsequent reports. For example -- you would be able to open the report below in the report painter:
-SET &COUNTRY='ENGLAND';
TABLE FILE CAR
PRINT CAR
RETAIL_COST
WHERE COUNTRY EQ '&COUNTRY';
END
Whereas, you would NOT be able to open this one in report painter:
TABLE FILE CAR
PRINT CAR
RETAIL_COST
-SET &COUNTRY='ENGLAND';
WHERE COUNTRY EQ '&COUNTRY';
END
Both reports produce the same results... This obviously is a very simple example, but should give you the idea of what I mean. Production: 7.6.6 WF Server <=> 7.6.6 WF Client <=> 7.6.6 Dev Studio Testing: <none> Using MRE & BID. Connected to MS SQL Server 2005 Output Types: HTML, Excel, PDF | |||
|
| <kimo> |
Thank You trav I'm still feeling my way around the IBI software and trying to stay out of trouble. | ||
|
| Platinum Member |
Staying out of trouble is a futile effort, I wouldn't worry about it. Seriously though, I was in your shoes about a year and a half ago and was trying to make sure everything we did was able to be opened in the GUI. Admittedly, having that goal in mind at first isn't necessarily a bad thing -- especially when you're not strong in the FOCUS code yet. But honestly, as you start to build more complex reports, I think you'll find yourself wanting to get into the code more and not as worried about whether or not it will open in the GUI. Frankly, there will be things you'll want to do that the GUI will "limit" you on -- so I would just keep an open mind and let those easy reports flow like normal but when the hard ones come along, don't let that be a roadblock. Production: 7.6.6 WF Server <=> 7.6.6 WF Client <=> 7.6.6 Dev Studio Testing: <none> Using MRE & BID. Connected to MS SQL Server 2005 Output Types: HTML, Excel, PDF | |||
|
| Guru |
The GUI is great for styling the report, drilldowns and other features. Also, moving into the version 7 era the GUI is much more robust and you can stay with the graphic tools more for a lot of reporting. Additionally, the GUI seldom crashes anymore, which had been an issue in prior versions. As noted above you'll know when text edit is the way to go with defines, table file reports, dialog manager, etc. Please bear in mind that a lot of the FocalPoint folks grew up with the keyboard so sometimes it is a conditioned reflex to stay with text edit. (We also grew up with black-and-white television, 8 tracks, ethyl gas, etc.) Sandy Kadish Dev: 8.2.04- PostgreSQL Test: 8.2.04 - PostgreSQL Prod: 8.2.04 - PostgreSQL | |||
|
| Expert |
Hey Sandy, What's the mouse for again?  Oh, and you forgot to mention Smokey Robinson!! T | |||
|
| <kimo> |
[quote] Thanks for the response all | ||
|
| Powered by Social Strata |
 | Please Wait. Your request is being processed... |
Read-Only TopicCopyright © 1996-2020 Information Builders
| View $GS_USERNAME's Public Profile |
| Add $GS_USERNAME to my Ignore List |
| View Recent Posts by $GS_USERNAME |
| Notify me of New Posts by $GS_USERNAME |