ApEx 3.0 BUG. Report Query Attributes

I found this bug when I tried to derive format from Page Item.
Here is my actions:
1.I create a Report Query.
2. Then I create RTF template.
3. Test it, it works.
4. Then I tried to change output format from pdf. It works.
5. I create Application item
6. Select Format "Derive from page item"
7. Choose my item and press "Apply Changes" button.
8. When I open my query again I can see "PDF".
9. I tried to change it several times, and I still can see "PDF" instead of "Derive from Page Item".
P.S. I use PI Publisher.
P.P.S. It works in Regular Print Report.
Best Regards, Kostya Proskudin

Kostya ,
Thanks for reporting this issue. That's a known problem, which we have already resolved, and we'll make this fix available with our upcoming patch release. Meanwhile, you can actually use those RTF templates with regular report regions, provided you have the same SQL statement in your report region, as you used in your report query. And for report regions, you actually can have the output format determined by an item.
Thanks,
Marc

Similar Messages

  • APEX BIP report query output format - not able to set with a variable

    I have a Named Columns (RTF) report that is working great, but I can't control the output format with a variable. I can set the "Output Format" in the Report Query Attributes, but it doesn't work when I set the report output format to "Derive from item". No matter what the item contains, I always get PDF output. I can see the variable in my session, but it doesn't control the output format. I have tried using the values "xml", "XML", "rtf", and "RTF".
    Any help would be appreciated...

    My guess is that an exception is being thrown for some rows. Since you've stubbed out your catch phrase to do nothing you're not going to have any visibility into what exception was thrown. You need to put some kind of logging in the catch phrase to see
    what is happening.

  • Passing Parameters to a report query

    I have built a report query, the query has 3 parameters.
    select * from EMP_DETAIL
    where
    emp=:EMPP
    and loc=:LOCP
    and seq=:SEQP
    When I test the query, enter the parameters manually, it renders and I get my report.
    When I add this layout to a standard on screen report region, I can not figure out how to pass the column values to those parameters.
    I'll try to explain. I have a report
    SELECT * FROM EMP
    The users can filter the report down, then when they find the emp they want, I have created a report link that is supposed to run the detail query and have the detail report come up in a PDF.
    So lets say they choose employee 0009, the columns have the :LOCP and the SEQP
    I want the report query for the PDF print to be filled in and the report rendered and printed. Like I said, I can test the report query/layout from the shared components section but I can not get the column values of say #EMP#,#LOC#,#SEQ# passed to the report.
    When I click the report, it appears to run forever. I do not know what is being passed to the report query.

    Starting to wonder if my question doesn't make sense.
    Does not seem to be something that hard.
    I have a APEX 3.0 stored report query and layout loaded via the shared components section. The stored report accepts 3 parameters.
    I have an employee report region (Select * from emp) and I have a derived link column that has a pretty picture in it. What I want to happen is when the users naturally migrate towards the bright colors on the screen in front of them and peck away at the mouse button, the values of the corresponding 3 columns are passed to the stored report and the report is ran and a PDF pops up and surprises the little buggers... sorry users that they actually managed to do something other than whine.
    Ideas, any takers?
    Maybe I will have to start a new thread with subject of
    "PLZ HELP MZ URGENT!!!!!! PLZ PLZ "
    or
    "ORACLE IS STUPIDO!!!"
    Those seems to get a lot of replies, some even helpful :)

  • Apex 3.0 bug? - report add column

    Hi
    I do not know about I have to post this on the "Comment apex 3.0 page" or here.... May be I have found a bug... please look at this
    When I create a Report with the Wizard, and add som column of at table to the report. Afterwards I add some more columns from the same table (on the report -> Query Definition -> "Add/remove columns".
    When I try to run the page I got the error:
    failed to parse SQL query:
    ORA-00918: column ambiguously defined
    I see in the qurey, there is add one more from statment, but it is the same as the first statment.....? I know it is the same table I add a column from but... or is it just me...
    "DEMO_CUSTOMERS"."CUSTOMER_ID" "CUSTOMER_ID",
    "DEMO_CUSTOMERS"."CUST_STREET_ADDRESS1" "CUST_STREET_ADDRESS1",
    "DEMO_CUSTOMERS"."CUST_STREET_ADDRESS2" "CUST_STREET_ADDRESS2",
    "DEMO_CUSTOMERS"."CUST_CITY" "CUST_CITY",
    "DEMO_CUSTOMERS"."CUST_STATE" "CUST_STATE",
    "DEMO_CUSTOMERS"."CUST_POSTAL_CODE" "CUST_POSTAL_CODE",
    "DEMO_CUSTOMERS"."PHONE_NUMBER1" "PHONE_NUMBER1",
    "DEMO_CUSTOMERS"."PHONE_NUMBER2" "PHONE_NUMBER2",
    "DEMO_CUSTOMERS"."CREDIT_LIMIT" "CREDIT_LIMIT",
    "DEMO_CUSTOMERS"."CUST_EMAIL" "CUST_EMAIL",
    "DEMO_CUSTOMERS"."CUST_FIRST_NAME" "CUST_FIRST_NAME",
    "DEMO_CUSTOMERS"."CUST_LAST_NAME" "CUST_LAST_NAME"
    FROM
    "#OWNER#"."DEMO_CUSTOMERS" "DEMO_CUSTOMERS",
    "#OWNER#"."DEMO_CUSTOMERS" "DEMO_CUSTOMERS"

    Query is:
    SELECT
    "FLOWTYPECATEGORIES"."FLOWTYPECATEGORY_ID" "FLOWTYPECATEGORY_ID",
    "FLOWTYPECATEGORIES"."FLOWTYPECATEGORY" "FLOWTYPECATEGORY",
    "FLOWTYPECATEGORIES"."VALID" "VALID",
    "FLOWTYPECATEGORIES"."TREND" "TREND"
    FROM
    "#OWNER#"."FLOWTYPECATEGORIES" "FLOWTYPECATEGORIES",
    "#OWNER#"."FLOWTYPECATEGORIES" "FLOWTYPECATEGORIES"
    there is table name duplicated.
    When I remove new column "TREND" then query is:
    SELECT
    "FLOWTYPECATEGORIES"."FLOWTYPECATEGORY_ID" "FLOWTYPECATEGORY_ID",
    "FLOWTYPECATEGORIES"."FLOWTYPECATEGORY" "FLOWTYPECATEGORY",
    "FLOWTYPECATEGORIES"."VALID" "VALID"
    FROM
    "#OWNER#"."FLOWTYPECATEGORIES" "FLOWTYPECATEGORIES"
    and everything is OK.

  • Ora-06502 pl/sql numeric or value error in Report Query in oracle apex

    Hello all,
    I need your help...
    ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    I am using bi publisher to generate PDF reports in oracle apex.
    We were using APEX 4.0 and migrated to 4.2 just a week ago.
    Now we have apex 4.2.
    When I try to Create report query,
    Shared Components >> Report Queries then create.
    and test a report in a create wizard I am getting a error "ORA-06502: PL/SQL: numeric or value error: character string buffer too small".
    I have also applied a patch "16760897".
    This issue is because of number of columns in a query is more then 26.
    If I run a report with 26 or less number of columns then the is working fine, otherwise getting this error.
    My before migration report queries working perfectly even now, but not new queries.
    This issue is also in apex.oracle.com.
    You can see
    Not working  - http://apex.oracle.com/pls/apex/f?p=619:4
    Working - http://apex.oracle.com/pls/apex/f?p=619:2:
    Please give a solution.
    Thanks you.

    check the DB version compatibility with apex 4 or your DB version to apex 4.0 support for upgrade!
    Oracle Application Express Installation Requirements for 4.0

  • APEX 4.0 Report Query column limitation, 43 column maximum for the result!

    Hi there,
    I'm trying to generate report from Apex 4.0.1, but I got stucked with column limitation when I'm executing the report query.
    Case:
    Environment: oracle 11g, apex 4.0.1, oracle BI 11, windows xp
    Table: My test table is quite simple, by creating a sample table with 44 columns, the column name is random, i.e. column1..column44, column data type is varchar2 (20)
    report query:my report query is also simple, by "select * from testtable"
    Ｄａｔａ: no data in my sample table
    Ｅｒｒｏｒ：　then I'll get the error: "HelpORA-06502: PL/SQL: numeric or value error: character string buffer too small"
    solution:　If I shrink the table column from 44 to 43, then the report can be generated to xls, pdf, etc.
    Question: Is there any column limitation for Apex report query? I know there's a 32k row size limitation for varchar, but since there's no single data in my table, it shouldn't be the case.
    Does anybody get this issue before? Thanks for any generous input!! :)
    Horatio

    hi marko,
    Thanks for the reply, but i can't find the 45 column limitation from report query and report printing. any clue for this call?
    Regards
    Horatio

  • Report query XML schema error - Apex Listener 2

    I built a simple query: select * from emp in (Shared components > Report Query)
    When I try to download XML schema for this query (Source Query section) resulting xsd file contains this text: String index out of range: -1
    Shared Apex hosting: 4.2.2.0.0.11
    Print server: Apex Listener 2.0.1

    Hey Saymonc, we're you ever able to find the cause of this issue?  I'm having this happen to me as well.  When I begin using the Report Query functionality, the schema downloaded just fine.  I made an update to a query and began receiving this error.  Now I get the error for ALL of my report queries.  I tried removing them and recreating them, and I continue to receive this error in my schema file, no matter how simple the query.  The data will download just fine, and using the Test Report button works as well.
    Thanks,
    Chris

  • How to change report query dynamically in Oracle APEX?

    Hi,
    I want to dynamically change the where condition in APEX report query. Can anyone help me solve my this problem?
    (Just want to change the query which we change in Oracle Reports using lexical parameter to change &Where, &Order by etc. dynamically!!)
    Thanks, Praful

    Hi
    I've been using flexible queries in APEX for a few years now, and your question just added a whole new dimension to the flexible and powerful nature or writing reports in APEX.
    While APEX Interactive reporting has almost completely removed the need the equivalent of Lexicals in Oracle Reports, I thought it might be fun to try and use lexicals in an APEX report.
    Before we start I should summarise the powerful capability of APEX reporting to have oprtional parameters (lots and lots of them if this is needed).
    For each parameter, you simply add a page item which will hold the value of the parameter.
    The item/parameter can be populated by typing in the value, defining an LOV, using a date-picker etc.
    To make the parameter optional simply use an OR in the where clause.
    So for a apge item P200_PARAM1.....include
    WHERE (:P200_PARAM1 IS NULL
    OR COLUMN1 = :P200_PARAM1)
    This way you can either leave the page item null or type in / select a value from a LOV.
    There is a small quirk in APEX LOV's which sometimes returns a value of '%' or '%null%' - depending on the version - when no value is selected.
    See Patrick Wolf's solution for this at Re: Null value handling in LOVs
    I include this Application Process in all my APEX applications ;)
    Now let's look at using the equivalent of Oracle Reports Lexicals......
    First-off - this is based on the APEX SQL report - NOT Interactive Report.
    It relies on the fact that you can let the query be parsed only at runtime.
    1. Define an SQL report entering the 'core' of your query.
    With a query like SELECT ENAME, JOB FROM EMP
    Select 'Generic Columns' option in the 'Column Headings' section
    Finish the report creation
    2. Define a page item - say P200_LEXICAL - type text on the page
    3. Edit the report and update the SQL query to include your lexical page item
    SELECT ENAME, JOB FROM EMP &P200_LEXICAL. (REMEMBER THE '.' AT THE END)
    Ensure that the option "Use Generic Column Names (parse query at runtime only)" is selected at the bottom of the query
    4. Add a button to the page -using 'Create a button displayed among this region's items' the will submit the page.
    5. Run the page - you will see all the employee names and job desdriptions
    6. Enter a where clause into the 'Lexical' textbox - say "WHERE ENAME LIKE 'K%'" and click the 'Go' button
    Voila! your where clause is magically applied.
    Try any variant you like adding an ORDER BY clause etc...... this is FUN!
    7. Clear the value of the LEXICAL and click go.
    Edit the report and move the &P200_LEXICAL. into the selected columns (or add another one)
    SELECT ENAME, JOB &P200_LEXICAL. FROM EMP
    8. Run the page
    Enter ",SAL" in the textbox and "Go"
    We can add as many columns as we like (subject to the "Maximum number of generic report columns:" set below the SQL query in the report edit section)
    Now because we have all the flexibility in APEX of setting page items using SQL or PLSQL you can set the value of the lexical programatically, or just pre-set a few values in an LOV - the options are limitless.
    While I've never had the need to use lexicals - you can see that APEX provides the most Flexible Lexicals in town.
    Eat your heart out "Oracle Reports"!!!
    Have fun
    Mike

  • 32k Rowsize Limit (ORA-006502) for Report Query Shared Objects in Apex 4.1

    We're trying to move legacy reports off of PlanetPress into Apex. One of the report queries has over 20 tables and attempting to run with the "Test Report" button in the Edit Report Query screen gets the error message:
    Error ORA-06502: PL/SQL: numeric or value error: character string buffer too small
    This problem appears to have been characterized previously here:
    Listener Error - character string buffer too small (ORA-06502)
    If I comment out 13 lines/items in my SELECT clause, the Test Report runs okay. If I add back in an innocuous literal sellect of a 100-character string, it goes back to the 6502 error.
    I was trying to add more literal strings to force APEX to shift internally from a 32k-limit to a CLOB for the row, however, with a 32k literal string in my SQL statement, APEX crashes. I can't strip out columns from my SQL as all are needed for the report.
    I would very much appreciate a work-around or a patch to Apex 4.1 to address this limitation. Thank you.

    Try moving some of your select logic into a view, thus you can select from the views and reduce your code... (Move the joining between tables and such to the view..)
    Thank you,
    Tony Miller
    Webster, TX

  • Shared Components APEX Report Query and Layout

    Does anyone know how to call the report query and layout from the Shared components section from a page within the application?

    mtbdude40 wrote:
    What I need is this:  The ability to create a PDF report with a custom header defining the data (example - select * from emp where deptno = :deptno and the header includes the department name).
    I use this white paper as my source:  http://www.oracle.com/technetwork/developer-tools/apex/learnmore/custom-pdf-reports-1953918.pdf
    You need to build and use a Shared Resource -> Report Queries.
    The Report Query will have two queries associated with it (see below).
    one query will be for the header information, the other will be for the data.
    use the "download" of the "xml data" as your source for Altova/other tools.
    If you add/remove/change queries, You'll have to redo your report (from scratch) as that changes the XML Schema required. (at least, with my experience)
    Once you get the hang of it, 2x queries is easy (Header, data)
    I've experimented with 3x queries (header, master,details) but have been unsuccessful.  I have some ideas though ("link" master->detail info via XPath stuff within Altova) but haven't gotten around to testing it.
    If you want to run the report for multiple departments....That might require some finesse.
    Unfortunately, the Source of the Queries can't be a scalar SQL that returns 1 row of 1 column of data type XMLType....
    MK

  • Bind Variables and Shared Component Report Query

    I have a query in a region report which I have replicated to a shared component report query.
    Both queries reference page items as bind variables in the where clause.
    The report region on screen shows the correct results but the report query shows "no data". This is the case when running "Test Query" and "Download XML data" from the shared component report query definition. If I hardcode the variable names I get rows returned, If I use bind variables - and specify the values for these variables I get no data. THe XML file contains the tags for each bind variable I have specified but has no data between the tags. I have Ticked the box to include application and session state but it appears that the bind variables are not being used.
    When I use my report query in the application (URL tied to a button) I get the same problem, the binds are not being passed to the report query.
    Can someone please clarify if this is a bug or not? And if not, how can I get it to work.
    I am using Apex 4.0.2
    Thanks
    Kathryn

    Hi
    To confirm, yes I selected the bind variables. I used these in the report layout, but the xml file has them as empty i.e.
    <P0_START_DATE><P0_START_DATE/> with nothing in between.
    IN the Test Query section, if I put real values in the boxes for the bind variables, I get no data found. If I hardcode the values into the query, I get the data.
    I've repeated the create report query many times and have created a report layout in RTF. I can use the layout with my region - in the print attributes and the layout works with the query but I need to create a PDF using 2 queries - ROWSET1 and ROWSET2. I can generate the XML but the values in the rows are all empty. When I use the layout with a report query instead of the region, I get no data even though I have used the same sql and have selected the bind variables. I was using variables from page items on page zero but have also tried using page items on the current page, the result is the same.
    I need to use a report query and a report layout as I need data from 2 queries in the PDF.
    I looked at your demo - what happens if you add a second sql query to the report query - is there any chance I can look at the back end (developer access?)
    Thanks for your input
    Kathryn

  • A Bug in "Print Attributes" tab in IR?

    Project Environment:
    Database: Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
    Apex : Application Express 3.1.1.00.09
    Also....: apex.oracle.com
    Problem scenario:
    I created an Interactive Reports (IR) in my project and tried to configure the "Download" PDF. It worked fine on "Classic Report". But for IR, it never worked. I'm facing multiple problems. They are:
    A. PDF report is blank.
    B. Sometime Acrobat Reader says "could not open <file name> because it is either not a supported file type or because the file has been damaged...)"
    When open the same file in a text editor, I can see the following:
    ORA-06502: PL/SQL: numeric or value error
    ORA-06512: at "FLOWS_030100.WWV_FLOW_RENDER_QUERY", line 636
    ORA-06503: PL/SQL: Function returned without value
    I then thought I could be missing something in the config. So wanted to create a sample IR in apex.oracle.com and see what happens. The following is the result:
    Notes:
    A. Please use IE to test this. Also untick "Disable script debugging (Internet Explorer)" from "Tools->Internet Options->Advanced". It works ok in Firefox, I believe.
    B. You can simulate this in apex.oracle.com (at least I was able to!!)
    Steps:
    1. Create an IR as normal. Say, App ID=46305, Page ID=6 and Region Name=Sample Interactive Report. Dont configure the "Print" settings yet.
    2. Once done and tested to see if it works ok.
    3. Now open Page (6) where you have the IR and click on the name, i.e. "Sample Interactive Report".
    4. We get "Edit Region" page with three tabs:
    a. Region Definition (current tab)
    b. Report Attributes
    c. Print Attributes
    5. Click "Print Attributes" tab
    6. Because the "Disable" flag is unticked (as per the note above), this will pop-up an error message:
    A Runtime Error has occurred.
    Do you wish to Debug?
    Line: 1
    Error: Object required.
    7. You can choose "No" to ignore it. But I tried "Yes" to see what the error is. The error is in the line:
    document.getElementById('P774_PRINT_FORMAT').value!='%null%'
    Clearly it is going to P774 and doesn't find P774_PRINT_FORMAT field and so the error. Is there a fix? How come it is not giving error in Firefox? Or should I enable / disable something in Firefox o get this error? And the most importantly how to avoid this error?
    8. Further on... if you go into "Report Attributes" and click the edit button on one of columns and then click "Print Attributes" tab, it goes to P960 and no errors!!
    9. Why does "Print Attributes" links from the main tabs (Report Definition and Report Attributes) go to P774 and from "Dynamic Query Attributes" goes to P960?
    10. Also, In P960, the "Report Columns" section says "Report returned no rows.". Is this normal in IR?
    Ultimately, although I can configure my Apex to use "BI Publisher" installation to create my PDF outputs from "Classic Reports", I couldn't do from IR.
    Seeking Answers For:
    1. Why PDF output of the IR report produces 0k file (and so blank report) when the screen displays records? This is common in my project as well as in apex.oracle.com. What am I missing?
    2. How to get rid of "ORA-06512: at "FLOWS_030100.WWV_FLOW_RENDER_QUERY", line 636"?
    3. Is there patch for this conflict between links accessing the "Print Attributes" pages (P774 and P960) as explained in the "Steps" above.

    Hello,
    The error
    2. How to get rid of "ORA-06512: at"FLOWS_030100.WWV_FLOW_RENDER_QUERY", line 636"?you can also find in the new features application. I wrote a post about that some days ago:
    Bug in New Features Application?
    Had some trouble to get the PDF print working, too. Printing works fine for standard reports, but for interactive report I am not able to get it working. Sometimes I am getting only blank pages (and no file) and sometimes I am getting PDF's which just contain an internal 500 error. Some details are in this thread: Print Interactive Reports does not work
    Maybe that's related to the error of kkkannan74.
    Regards, Tine.

  • CSS Style (report column attributes) not working

    I found the CSS Style settings for a report column only seem to work if using a "Standard Report Column". Since the report is wider than the screen, some columns are wrapping, making the report not-that-nice readable.
    Unfortunately I have the need to define some report columns where undesired wrapping occurs as "Display as Text (based on LOV, does not save state)" and tried to avoid wrapping using "white-space:nowrap;" or specifying a fixed width, but it seems I'm out of luck - is there a way around this (other than performing the report query using a huge DECODE clause and setting the column to "Standard Report Column" again, which somewhat renders the LOV useless except for the select list on the data entry form)? This is happening on APEX 3.12.
    Furthermore - is this expected behaviour?
    Thanks in advance,
    Holger

    Furthermore - is this expected behaviour?Looks like it, or it is a [long-standing bug|http://forums.oracle.com/forums/thread.jspa?messageID=1126613]. I've tried it (although only have access to APEX 3.0 at present) and none of the CSS class/style/custom attributes from Column Formatting or Tabular Form Element are being applied. If it's not a bug then it should be raised as an enhancement request.
    In the meantime you'll need to work round it.
    other than performing the report query using a huge DECODE clause Is that necessary due to a static LOV? If it's dynamic based on a table/view then get the look-up value in the query via a join or scalar subquery so you have a Standard Report Column and can use the CSS class/style/custom attributes from Column Formatting.
    Alternatively, stick with the Display as Text from LOV and create a custom named column report template using [colgroup/col|http://reference.sitepoint.com/html/colgroup] to specify fixed width columns.

  • APEX, BI Publisher and SQL Query (PL/SQL Function returning SQL Query)..

    I don't know if I should be posting this in this Forum or the BI Publisher forum, so I am posting in BOTH forums..
    I love APEX, let me say that first.. And appreciate the support offered here by the group, but am running int a confusing issue when BI Publisher tries to build a report from the above type APEX report..
    Here is my dilemma:
    I have a number of reports that are part of a Oracle package. They return an SQL Query back to a reports region on a page. I am having to deal with the column names returned are col01, col02..
    The issue I have is, when building the Application Level query to download the XML sample from in building RTF layouts in Word, you can not use this code, you MUST use a standard SQL Select.
    I have taken the sql from the function returning sql, and copied into the application query, supplying the required data values for bind variables being used in the query.
    An XML file is produced, and I use this to build the RTF format file that I load back into APEX and try to use it for the PDF rendering of the report. I can view the output as a PDF in the Word add on, but when I try using it with the report, it is returning an empty PDF file.
    Can anyone tell me what error log files on the bi publisher side I can look at to see what error is happening?
    Thank you,
    Tony Miller
    UTMB/EHN
    Title changed, maybe SOMEONE has an idea on this??
    Message was edited by:
    Tony Miller

    Hi,
    1/ first check you are passing the bind variables and
    appropriate values in the call to your report - if
    the query returns no data then you get an empty page
    So if your query takes :P10_USERNAME variable then
    pass it to the report in the URL
    f?p=&APP_ID.:0:&SESSION.:PRINT_REPORT=YOUR_REP_QUERY_N
    AME:::P10_USERNAME:MYUSER
    2/ try to use the Default layout first to check your
    report query really returns the data when called
    3/ if you defined a header in your rtf template check
    there is no & (ampersand) - if using & in the header
    and preview the template from word it displays data
    OK, but if you use this template in the report query
    it fails to render the data (bug in Apex-> Bi
    Publisher integration maybe?)
    4/ If using the table in the rtf template check its
    width does not overflow the page margins - there is a
    problem with pdf export
    5/ check
    /oc4j/j2ee/home/application-deployments/xmlpserver/app
    lication.log forthe information on BI Publisher runs
    RadoIssue was in the APEX page having issues.. I recoded a new page and am able to generate BI Publisher based PDF files..
    Thank you,
    Tony Miller
    UTMB/EHN

  • Bug report: Copy page - Highlight report keyword

    Minor bug
    I have a page with a report region and a search text field P1_SEARCH and this is used as &P1_SEARCH. in the Highlight words attribute of some of the report columns.
    When I use the Copy Page wizard to copy this to Page 2, the wizard creates the P2_SEARCH item but the Report Column attributes still refer to &P1_SEARCH. so the highlighting doesn't work.
    Thanks.

    Hi,
    just discovered, that the "Copy Page Wizard" doesn't copy the "Static ID" of regions.
    Patrick
    My APEX Blog: http://www.inside-oracle-apex.com/
    The APEX Builder Plugin: http://builderplugin.oracleapex.info/ New
    The ApexLib Framework: http://apexlib.sourceforge.net/

Maybe you are looking for