I have a datasource with many thousands of records but only a handful of unique values for a specific parameter. When I create an HTML launch page I can either code the individual choices or tell it to dynamically populate. If I set it to dynamically populate it takes a while for WebFOCUS to find the unique values to return.
Is there a way to code this list into the synonym?
My concern is for the users who are creating their own reports with Report Assistant. I don't want to have to tell them to use a separate 'lookup' data source for creating parameters but if they use the original data source it takes a long time for their lists to populate.
I'm sure some of you out there have found a way to address this. If you'd be willing to share your concepts with me I'd be very thankful!
Regards,
Dan PinaultThis message has been edited. Last edited by: Dan Pinault,
7.7.05M/7.7.03 HF6 on Windows Server 2003 SP2 output to whatever is required.
October 27, 2008, 03:16 PM
hammo1j
Dan
Ideally you would expect RA to take ACCEPT attribute ahead of searching the whole file but it doesn't.
RA needs to change but prob will stay static as other stuff comes to the fore.
John
Server: WF 7.6.2 ( BID/Rcaster) Platform: W2003Server/IIS6/Tomcat/SQL Server repository Adapters: SQL Server 2000/Oracle 9.2 Desktop: Dev Studio 765/XP/Office 2003 Applications: IFS/Jobscope/Maximo
October 28, 2008, 06:48 AM
Danny-SRL
Dan, What is your data source? If it is something that you can change, can you make it a Focus file? If so, you could build a hierarchy with your parameter as the root segment and the rest of the data in a child segment. You root segment would then only occupy a block of data and retrieval of the field would be immediate.
Daniel In Focus since 1982 wf 8.202M/Win10/IIS/SSA - WrapApp Front End for WF
October 28, 2008, 10:53 AM
Dan Pinault
John - Yes, I was hoping that I could make use of the ACCEPT attribute in the synonym but, as you said, that doesn't do it. I think I'll submit a New Feature Request just to get it on record.
Daniel - My data source is MS SQL.
I guess I'll have to stick with the method of creating a small 'lookup' table and train my users to use that.
Thanks for your input!
Dan
7.7.05M/7.7.03 HF6 on Windows Server 2003 SP2 output to whatever is required.
October 28, 2008, 12:24 PM
Charlz
It sounds like the real problem, underlying Dan's problem, is way too much redundant data in the data source ?
It seems that reading thousands of records to get a handful uses a lot of resources for little result.
If it is possible, can you (or your DBA) segregate the 'handful of unique values' for that parameter into its own segment ?
That sounds like it would save a lot of time since no one would have to write special code to extract the unique values ?
If it's something you can change, then yes, you'll have to code around it. Maybe write a function that extracts the unique values and put it in a library for future developers who will work on this data source ?