Bug in copying report with PLSQL region...

Where can i send about one possible bug...so it should not be public (picture shows sensitive debug infos) ...and it looks enough for finding problems?
Scott (I owe you one bug report. here is chance to revanche?)
THX!
Application Express 2.2.1.00.04
Oracle 10.2.0.2

I have sent you at first time mail with "rar, www.rarlab.com" in attachment.
Then I have sent you mail without attachment.
So I ask where (how !?) to send attachment!?

Similar Messages

Is this a bug or a feature with audio regions?

ok so I have an audio part in a project then copy/paste in a later part of the arrangement and after that change the size of the new copied part with the mouse(dragging from the end of it)it changes and messes up the original version as well. I just recently switched to Logic from using Cubase so is this some feature of having the regions linked together somehow or is it just working wrong?

I found the part that talks about how copy/paste is supposed to work, and it turns out that the manual describes how people want it to work instead of how the app actually works. It says that copy/paste makes a copy (a new region) and the two can be edited independently. Copy/paste is NOT supposed to create a clone.
Unfortunately, the app doesn't work the way the manual describes. Here's the relevant part from the manual:
"To copy a region (method 2):
1 Select the region, then choose Edit > Copy (or use the Copy key command,
default: Command-C).
This copies the selected region to the Clipboard.
2 Set the desired playhead position by clicking on the Bar ruler.
3 Choose Edit > Paste (Command-V) to paste the contents of the Clipboard into the
Arrange. The paste will occur on the selected track at the playhead position.
If several regions are selected, their relative time and track positions are retained. "
"*Copied regions are actually true, independent replicas of original regions. Changes*
*made to a parent region will not affect child copies.*
If you want this type of behavior—where changes to the parent region affect child
regions—make use of the Loop function (see “Looping Regions” on page 329), or
create cloned or alias regions (see “Repeating Regions” on page 324).
*When you copy an audio region, a new region is automatically created in the Audio Bin.*
*The new region will retain the name of the original, with a sequential number added.*
As an example, kickingloop.1 will be the name of a region copy, if the original region is
called kickingloop. A second copy will be named kickingloop.2, a third kickingloop.3,
and so on."
Looks like either the manual or the app is wrong. Hopefully apple will actually read the bug reports and fix the app.

Downloading Reports - with other regions

Hi,
We are re-writing a web report application in APEX. Our current system "regions" for the report description and report parameters. When you export/download the report these regions are included in the csv file.
Is their a way we can do this in APEX? We don't have BI publisher.
Thank you,
Martin

Hi Fred Narthasilpa,
I have searched thru some of the Oracle Manuals for the same and found that they will provide support to Websphere soon, to publish Oracle Reports.
However, not sure whether the same is made avl. as of today.
Have a nice day,
Raja Angamuthu B

Re: BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns

Hello Everyone.
I've run into something quite strange and am hoping you can help me.
I am using Apex 4.0.1 and Oracle version 10.2.0.5. I've created a "classical" report in which the underlying SQL is a very simple:
select * from pvtabThe Oracle table pvtab consists of 419 columns, all of which are varchar2(88) and number type. That's it.
When I run the report, al of the columns show up as expected.
However, when I go into the "Report Attributes" tab and click on one of the fields (any of them, it doesn't matter which one), I immediately get the following error:
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "598CAA7B68746A66F4B99E1512C36DED" application checksum = "0"If if replace the "*" with a few actual column names, then I am able to access any of these columns without problem.
If I put back the "*", I then encounter this error again.
I have never seen this error with other SQL SELECT statements in which I use the "*" qualifier to retrieve all columns from the table.
And so, I am wondering if the error is caused because of the large number of columns (419) in my table.
I've seen this same error mentioned in connection with forms but never with a report.
So, is there some limit to the number of columns one can have in a "classic" or interactive report?
Any idea why I would be getting this error?
Here is the DDL for my table pvtab:
CREATE TABLE "PVTAB"
   (     "MICRO" VARCHAR2(4),
     "PRIM" VARCHAR2(4),
     "UNIT" NUMBER,
     "SEC_REF_1" NUMBER,
     "SECN_1" VARCHAR2(88),
     "SEC_REF_2" NUMBER,
     "SECN_2" VARCHAR2(88),
     "SEC_REF_3" NUMBER,
     "SECN_3" VARCHAR2(88),
     "SEC_REF_4" NUMBER,
     "SECN_4" VARCHAR2(88),
     "SEC_REF_5" NUMBER,
     "SECN_5" VARCHAR2(88),
     "SEC_REF_6" NUMBER,
     "SECN_6" VARCHAR2(88),
     "SEC_REF_7" NUMBER,
     "SECN_7" VARCHAR2(88),
     "SEC_REF_8" NUMBER,
     "SECN_8" VARCHAR2(88),
     "SEC_REF_9" NUMBER,
     "SECN_9" VARCHAR2(88),
     "SEC_REF_10" NUMBER,
     "SECN_10" VARCHAR2(88),
     "SEC_REF_11" NUMBER,
     "SECN_11" VARCHAR2(88),
     "SEC_REF_12" NUMBER,
     "SECN_12" VARCHAR2(88),
     "SEC_REF_13" NUMBER,
     "SECN_13" VARCHAR2(88),
     "SEC_REF_14" NUMBER,
     "SECN_14" VARCHAR2(88),
     "SEC_REF_15" NUMBER,
     "SECN_15" VARCHAR2(88),
     "SEC_REF_16" NUMBER,
     "SECN_16" VARCHAR2(88),
     "SEC_REF_17" NUMBER,
     "SECN_17" VARCHAR2(88),
     "SEC_REF_18" NUMBER,
     "SECN_18" VARCHAR2(88),
     "SEC_REF_19" NUMBER,
     "SECN_19" VARCHAR2(88),
     "SEC_REF_20" NUMBER,
     "SECN_20" VARCHAR2(88),
     "SEC_REF_21" NUMBER,
     "SECN_21" VARCHAR2(88),
     "SEC_REF_22" NUMBER,
     "SECN_22" VARCHAR2(88),
     "SEC_REF_23" NUMBER,
     "SECN_23" VARCHAR2(88),
     "SEC_REF_24" NUMBER,
     "SECN_24" VARCHAR2(88),
     "SEC_REF_25" NUMBER,
     "SECN_25" VARCHAR2(88),
     "SEC_REF_26" NUMBER,
     "SECN_26" VARCHAR2(88),
     "SEC_REF_27" NUMBER,
     "SECN_27" VARCHAR2(88),
     "SEC_REF_28" NUMBER,
     "SECN_28" VARCHAR2(88),
     "SEC_REF_29" NUMBER,
     "SECN_29" VARCHAR2(88),
     "SEC_REF_30" NUMBER,
     "SECN_30" VARCHAR2(88),
     "SEC_REF_31" NUMBER,
     "SECN_31" VARCHAR2(88),
     "SEC_REF_32" NUMBER,
     "SECN_32" VARCHAR2(88),
     "SEC_REF_33" NUMBER,
     "SECN_33" VARCHAR2(88),
     "SEC_REF_34" NUMBER,
     "SECN_34" VARCHAR2(88),
     "SEC_REF_35" NUMBER,
     "SECN_35" VARCHAR2(88),
     "SEC_REF_36" NUMBER,
     "SECN_36" VARCHAR2(88),
     "SEC_REF_37" NUMBER,
     "SECN_37" VARCHAR2(88),
     "SEC_REF_38" NUMBER,
     "SECN_38" VARCHAR2(88),
     "SEC_REF_39" NUMBER,
     "SECN_39" VARCHAR2(88),
     "SEC_REF_40" NUMBER,
     "SECN_40" VARCHAR2(88),
     "SEC_REF_41" NUMBER,
     "SECN_41" VARCHAR2(88),
     "SEC_REF_42" NUMBER,
     "SECN_42" VARCHAR2(88),
     "SEC_REF_43" NUMBER,
     "SECN_43" VARCHAR2(88),
     "SEC_REF_44" NUMBER,
     "SECN_44" VARCHAR2(88),
     "SEC_REF_45" NUMBER,
     "SECN_45" VARCHAR2(88),
     "SEC_REF_46" NUMBER,
     "SECN_46" VARCHAR2(88),
     "SEC_REF_47" NUMBER,
     "SECN_47" VARCHAR2(88),
     "SEC_REF_48" NUMBER,
     "SECN_48" VARCHAR2(88),
     "SEC_REF_49" NUMBER,
     "SECN_49" VARCHAR2(88),
     "SEC_REF_50" NUMBER,
     "SECN_50" VARCHAR2(88),
     "SEC_REF_51" NUMBER,
     "SECN_51" VARCHAR2(88),
     "SEC_REF_52" NUMBER,
     "SECN_52" VARCHAR2(88),
     "SEC_REF_53" NUMBER,
     "SECN_53" VARCHAR2(88),
     "SEC_REF_54" NUMBER,
     "SECN_54" VARCHAR2(88),
     "SEC_REF_55" NUMBER,
     "SECN_55" VARCHAR2(88),
     "SEC_REF_56" NUMBER,
     "SECN_56" VARCHAR2(88),
     "SEC_REF_57" NUMBER,
     "SECN_57" VARCHAR2(88),
     "SEC_REF_58" NUMBER,
     "SECN_58" VARCHAR2(88),
     "SEC_REF_59" NUMBER,
     "SECN_59" VARCHAR2(88),
     "SEC_REF_60" NUMBER,
     "SECN_60" VARCHAR2(88),
     "SEC_REF_61" NUMBER,
     "SECN_61" VARCHAR2(88),
     "SEC_REF_62" NUMBER,
     "SECN_62" VARCHAR2(88),
     "SEC_REF_63" NUMBER,
     "SECN_63" VARCHAR2(88),
     "SEC_REF_64" NUMBER,
     "SECN_64" VARCHAR2(88),
     "SEC_REF_65" NUMBER,
     "SECN_65" VARCHAR2(88),
     "SEC_REF_66" NUMBER,
     "SECN_66" VARCHAR2(88),
     "SEC_REF_67" NUMBER,
     "SECN_67" VARCHAR2(88),
     "SEC_REF_68" NUMBER,
     "SECN_68" VARCHAR2(88),
     "SEC_REF_69" NUMBER,
     "SECN_69" VARCHAR2(88),
     "SEC_REF_70" NUMBER,
     "SECN_70" VARCHAR2(88),
     "SEC_REF_71" NUMBER,
     "SECN_71" VARCHAR2(88),
     "SEC_REF_72" NUMBER,
     "SECN_72" VARCHAR2(88),
     "SEC_REF_73" NUMBER,
     "SECN_73" VARCHAR2(88),
     "SEC_REF_74" NUMBER,
     "SECN_74" VARCHAR2(88),
     "SEC_REF_75" NUMBER,
     "SECN_75" VARCHAR2(88),
     "SEC_REF_76" NUMBER,
     "SECN_76" VARCHAR2(88),
     "SEC_REF_77" NUMBER,
     "SECN_77" VARCHAR2(88),
     "SEC_REF_78" NUMBER,
     "SECN_78" VARCHAR2(88),
     "SEC_REF_79" NUMBER,
     "SECN_79" VARCHAR2(88),
     "SEC_REF_80" NUMBER,
     "SECN_80" VARCHAR2(88),
     "SEC_REF_81" NUMBER,
     "SECN_81" VARCHAR2(88),
     "SEC_REF_82" NUMBER,
     "SECN_82" VARCHAR2(88),
     "SEC_REF_83" NUMBER,
     "SECN_83" VARCHAR2(88),
     "SEC_REF_84" NUMBER,
     "SECN_84" VARCHAR2(88),
     "SEC_REF_85" NUMBER,
     "SECN_85" VARCHAR2(88),
     "SEC_REF_86" NUMBER,
     "SECN_86" VARCHAR2(88),
     "SEC_REF_87" NUMBER,
     "SECN_87" VARCHAR2(88),
     "SEC_REF_88" NUMBER,
     "SECN_88" VARCHAR2(88),
     "SEC_REF_89" NUMBER,
     "SECN_89" VARCHAR2(88),
     "SEC_REF_90" NUMBER,
     "SECN_90" VARCHAR2(88),
     "SEC_REF_91" NUMBER,
     "SECN_91" VARCHAR2(88),
     "SEC_REF_92" NUMBER,
     "SECN_92" VARCHAR2(88),
     "SEC_REF_93" NUMBER,
     "SECN_93" VARCHAR2(88),
     "SEC_REF_94" NUMBER,
     "SECN_94" VARCHAR2(88),
     "SEC_REF_95" NUMBER,
     "SECN_95" VARCHAR2(88),
     "SEC_REF_96" NUMBER,
     "SECN_96" VARCHAR2(88),
     "SEC_REF_97" NUMBER,
     "SECN_97" VARCHAR2(88),
     "SEC_REF_98" NUMBER,
     "SECN_98" VARCHAR2(88),
     "SEC_REF_99" NUMBER,
     "SECN_99" VARCHAR2(88),
     "SEC_REF_100" NUMBER,
     "SECN_100" VARCHAR2(88),
     "SEC_REF_101" NUMBER,
     "SECN_101" VARCHAR2(88),
     "SEC_REF_102" NUMBER,
     "SECN_102" VARCHAR2(88),
     "SEC_REF_103" NUMBER,
     "SECN_103" VARCHAR2(88),
     "SEC_REF_104" NUMBER,
     "SECN_104" VARCHAR2(88),
     "SEC_REF_105" NUMBER,
     "SECN_105" VARCHAR2(88),
     "SEC_REF_106" NUMBER,
     "SECN_106" VARCHAR2(88),
     "SEC_REF_107" NUMBER,
     "SECN_107" VARCHAR2(88),
     "SEC_REF_108" NUMBER,
     "SECN_108" VARCHAR2(88),
     "SEC_REF_109" NUMBER,
     "SECN_109" VARCHAR2(88),
     "SEC_REF_110" NUMBER,
     "SECN_110" VARCHAR2(88),
     "SEC_REF_111" NUMBER,
     "SECN_111" VARCHAR2(88),
     "SEC_REF_112" NUMBER,
     "SECN_112" VARCHAR2(88),
     "SEC_REF_113" NUMBER,
     "SECN_113" VARCHAR2(88),
     "SEC_REF_114" NUMBER,
     "SECN_114" VARCHAR2(88),
     "SEC_REF_115" NUMBER,
     "SECN_115" VARCHAR2(88),
     "SEC_REF_116" NUMBER,
     "SECN_116" VARCHAR2(88),
     "SEC_REF_117" NUMBER,
     "SECN_117" VARCHAR2(88),
     "SEC_REF_118" NUMBER,
     "SECN_118" VARCHAR2(88),
     "SEC_REF_119" NUMBER,
     "SECN_119" VARCHAR2(88),
     "SEC_REF_120" NUMBER,
     "SECN_120" VARCHAR2(88),
     "SEC_REF_121" NUMBER,
     "SECN_121" VARCHAR2(88),
     "SEC_REF_122" NUMBER,
     "SECN_122" VARCHAR2(88),
     "SEC_REF_123" NUMBER,
     "SECN_123" VARCHAR2(88),
     "SEC_REF_124" NUMBER,
     "SECN_124" VARCHAR2(88),
     "SEC_REF_125" NUMBER,
     "SECN_125" VARCHAR2(88),
     "SEC_REF_126" NUMBER,
     "SECN_126" VARCHAR2(88),
     "SEC_REF_127" NUMBER,
     "SECN_127" VARCHAR2(88),
     "SEC_REF_128" NUMBER,
     "SECN_128" VARCHAR2(88),
     "SEC_REF_129" NUMBER,
     "SECN_129" VARCHAR2(88),
     "SEC_REF_130" NUMBER,
     "SECN_130" VARCHAR2(88),
     "SEC_REF_131" NUMBER,
     "SECN_131" VARCHAR2(88),
     "SEC_REF_132" NUMBER,
     "SECN_132" VARCHAR2(88),
     "SEC_REF_133" NUMBER,
     "SECN_133" VARCHAR2(88),
     "SEC_REF_134" NUMBER,
     "SECN_134" VARCHAR2(88),
     "SEC_REF_135" NUMBER,
     "SECN_135" VARCHAR2(88),
     "SEC_REF_136" NUMBER,
     "SECN_136" VARCHAR2(88),
     "SEC_REF_137" NUMBER,
     "SECN_137" VARCHAR2(88),
     "SEC_REF_138" NUMBER,
     "SECN_138" VARCHAR2(88),
     "SEC_REF_139" NUMBER,
     "SECN_139" VARCHAR2(88),
     "SEC_REF_140" NUMBER,
     "SECN_140" VARCHAR2(88),
     "SEC_REF_141" NUMBER,
     "SECN_141" VARCHAR2(88),
     "SEC_REF_142" NUMBER,
     "SECN_142" VARCHAR2(88),
     "SEC_REF_143" NUMBER,
     "SECN_143" VARCHAR2(88),
     "SEC_REF_144" NUMBER,
     "SECN_144" VARCHAR2(88),
     "SEC_REF_145" NUMBER,
     "SECN_145" VARCHAR2(88),
     "SEC_REF_146" NUMBER,
     "SECN_146" VARCHAR2(88),
     "SEC_REF_147" NUMBER,
     "SECN_147" VARCHAR2(88),
     "SEC_REF_148" NUMBER,
     "SECN_148" VARCHAR2(88),
     "SEC_REF_149" NUMBER,
     "SECN_149" VARCHAR2(88),
     "SEC_REF_150" NUMBER,
     "SECN_150" VARCHAR2(88),
     "SEC_REF_151" NUMBER,
     "SECN_151" VARCHAR2(88),
     "SEC_REF_152" NUMBER,
     "SECN_152" VARCHAR2(88),
     "SEC_REF_153" NUMBER,
     "SECN_153" VARCHAR2(88),
     "SEC_REF_154" NUMBER,
     "SECN_154" VARCHAR2(88),
     "SEC_REF_155" NUMBER,
     "SECN_155" VARCHAR2(88),
     "SEC_REF_156" NUMBER,
     "SECN_156" VARCHAR2(88),
     "SEC_REF_157" NUMBER,
     "SECN_157" VARCHAR2(88),
     "SEC_REF_158" NUMBER,
     "SECN_158" VARCHAR2(88),
     "SEC_REF_159" NUMBER,
     "SECN_159" VARCHAR2(88),
     "SEC_REF_160" NUMBER,
     "SECN_160" VARCHAR2(88),
     "SEC_REF_161" NUMBER,
     "SECN_161" VARCHAR2(88),
     "SEC_REF_162" NUMBER,
     "SECN_162" VARCHAR2(88),
     "SEC_REF_163" NUMBER,
     "SECN_163" VARCHAR2(88),
     "SEC_REF_164" NUMBER,
     "SECN_164" VARCHAR2(88),
     "SEC_REF_165" NUMBER,
     "SECN_165" VARCHAR2(88),
     "SEC_REF_166" NUMBER,
     "SECN_166" VARCHAR2(88),
     "SEC_REF_167" NUMBER,
     "SECN_167" VARCHAR2(88),
     "SEC_REF_168" NUMBER,
     "SECN_168" VARCHAR2(88),
     "SEC_REF_169" NUMBER,
     "SECN_169" VARCHAR2(88),
     "SEC_REF_170" NUMBER,
     "SECN_170" VARCHAR2(88),
     "SEC_REF_171" NUMBER,
     "SECN_171" VARCHAR2(88),
     "SEC_REF_172" NUMBER,
     "SECN_172" VARCHAR2(88),
     "SEC_REF_173" NUMBER,
     "SECN_173" VARCHAR2(88),
     "SEC_REF_174" NUMBER,
     "SECN_174" VARCHAR2(88),
     "SEC_REF_175" NUMBER,
     "SECN_175" VARCHAR2(88),
     "SEC_REF_176" NUMBER,
     "SECN_176" VARCHAR2(88),
     "SEC_REF_177" NUMBER,
     "SECN_177" VARCHAR2(88),
     "SEC_REF_178" NUMBER,
     "SECN_178" VARCHAR2(88),
     "SEC_REF_179" NUMBER,
     "SECN_179" VARCHAR2(88),
     "SEC_REF_180" NUMBER,
     "SECN_180" VARCHAR2(88),
     "SEC_REF_181" NUMBER,
     "SECN_181" VARCHAR2(88),
     "SEC_REF_182" NUMBER,
     "SECN_182" VARCHAR2(88),
     "SEC_REF_183" NUMBER,
     "SECN_183" VARCHAR2(88),
     "SEC_REF_184" NUMBER,
     "SECN_184" VARCHAR2(88),
     "SEC_REF_185" NUMBER,
     "SECN_185" VARCHAR2(88),
     "SEC_REF_186" NUMBER,
     "SECN_186" VARCHAR2(88),
     "SEC_REF_187" NUMBER,
     "SECN_187" VARCHAR2(88),
     "SEC_REF_188" NUMBER,
     "SECN_188" VARCHAR2(88),
     "SEC_REF_189" NUMBER,
     "SECN_189" VARCHAR2(88),
     "SEC_REF_190" NUMBER,
     "SECN_190" VARCHAR2(88),
     "SEC_REF_191" NUMBER,
     "SECN_191" VARCHAR2(88),
     "SEC_REF_192" NUMBER,
     "SECN_192" VARCHAR2(88),
     "SEC_REF_193" NUMBER,
     "SECN_193" VARCHAR2(88),
     "SEC_REF_194" NUMBER,
     "SECN_194" VARCHAR2(88),
     "SEC_REF_195" NUMBER,
     "SECN_195" VARCHAR2(88),
     "SEC_REF_196" NUMBER,
     "SECN_196" VARCHAR2(88),
     "SEC_REF_197" NUMBER,
     "SECN_197" VARCHAR2(88),
     "SEC_REF_198" NUMBER,
     "SECN_198" VARCHAR2(88),
     "SEC_REF_199" NUMBER,
     "SECN_199" VARCHAR2(88),
     "SEC_REF_200" NUMBER,
     "SECN_200" VARCHAR2(88),
     "SEC_REF_201" NUMBER,
     "SECN_201" VARCHAR2(88),
     "SEC_REF_202" NUMBER,
     "SECN_202" VARCHAR2(88),
     "SEC_REF_203" NUMBER,
     "SECN_203" VARCHAR2(88),
     "SEC_REF_204" NUMBER,
     "SECN_204" VARCHAR2(88),
     "SEC_REF_205" NUMBER,
     "SECN_205" VARCHAR2(88),
     "SEC_REF_206" NUMBER,
     "SECN_206" VARCHAR2(88),
     "SEC_REF_207" NUMBER,
     "SECN_207" VARCHAR2(88),
     "SEC_REF_208" NUMBER,
     "SECN_208" VARCHAR2(88)
   );Thank you for any help/advice.
Elie
Edited by: EEG on Jun 12, 2011 2:09 PM

So, is there some limit to the number of columns one can have in a "classic" or interactive report?Yes. See Oracle® Application Express Application Builder User's Guide Release 4.0, Appendix B: Oracle Application Express Limits.
Any idea why I would be getting this error?No, but I've replicated it in APEX 4.0.2.00.07 on 11.2.0.1.0 EE using a table of 420 <tt>varchar2(88)</tt> columns:
>
ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "50C9BDC0AA1AEF0EB272E9158B2117B4" application checksum = "0"
>
Happens whether using <tt>select *</tt> or including all column names in the query. (I know you don't want to type all the column names, but I'd never use <tt>select *</tt> in a production application: always use a proper column list. You can get one without typing by drag-and-drop of a table in most IDEs, or a query from <tt>user_tab_columns</tt>.)
I hit the problem at 274 columns. Such an arbitrary number leads me to think that the problem is not one of the number of columns per se, but is due to some other limit (possibly a 32K VARCHAR2/RAW buffer somewhere).
Workaround:
Updates to the report column attributes are actually being saved, and you can navigate them using the Page Definition tree view as described in Appendix B.
Getting More Help:
This is probably a bug. If you have a support agreement with Oracle raise an SR with Oracle Support.
Also:
<li>Search the forum using the "ORA-20503" code and other possible terms to see if there's anything relevant. I had a quick look but the only thread in this context recommended an upgrade on an Oracle 9 DB version that's not compatible with APEX 4.0.
<li>To get the attention of the Oracle APEX team or anyone else who may know more about this problem than we do, edit your original post and change the Subject to be more specific about the actual nature of the problem: <em>BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns</em>, and include your database version/edition and the definition of the <tt>PVTAB</tt> table.
Finally:
Somebody's bound to ask, so we might as well get started:
<li>Why so many columns?
<li>What requirement is this trying to fulfil?

Bug in PDF generation with Report Builder CF8

Hello
there is a bug in the calculation of the left margin of a
page.
I upgraded from MX 7.02 to CF8. My "old" Reports worked fine,
but when I export them to PDF an print them the left margin is
different.
I'm using metric settings in the Report Builder. I created a
new Report with Left Margin 2 cm and a single Field with the left
Property = 1 cm (0.9879 cm). The printed paper with these poperties
where fine. I could measure appoximatly 3cm . But if I use Report
Left Margin = 1.27 cm and Field left Property = 0.35cm. The left
margin of the printed paper is only 1.1cm.
So it depends on the choosen Values of report left margin and
the left property of a field.
Does anybody else have the same problem?

I found this posting as I have now "rediscovered" this issue. I came to the same conclusion - edit ALT TEXT for every image.
However, I think it is confusing that these paths of image file are not considered Personal Information that can be removed using the Inspect Document feature (I tried - was not successful). The list of things to be removed using this wizard is quite extensive
- and some of them less visible than these file paths.
It would be interesting to know if this is going to change with future updates of Word. Why is an ALT TEXT included at all per default? I think using the file path in ALT TEXT should be made optional. Is there a way to turn off this default embedding of
the full path?
As the OP I also used Office 2013 on Windows 7 64bit.
Elke

BUG: Popup in page fragment; with many regions and popup binded to backing.

BUG: Popup in page fragment; with many regions and popup or parent binded to backing bean.
JDEV11.1.2.1 Popup will not popup.(sometimes works if using RichPopup.Show() in backing bean Java code.)
I have a bug (Popup will not popup)that only happens when I have more than one of the same region.
And I have a popup in the page fragment is binded to backing bean.
My SR guy is out today but we plan to enter one.
test.jspx
<?xml version='1.0' encoding='UTF-8'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1" xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
          xmlns:f="http://java.sun.com/jsf/core">
    <jsp:directive.page contentType="text/html;charset=UTF-8"/>
    <f:view>
        <af:document title="test" id="d1">
            <af:form id="f1">
                <af:panelGroupLayout id="pgl1" layout="horizontal">
                    <af:outputText value="BUG JDEV11.1.2.1 and IE7. Broken Popup! If I have a jsff fragment and I have many regions of this fragment."
                                   id="ot2"/>
                    <af:outputText value="Inside the fragment I have a popup. If that popup or its parent are binded to a Backing Bean the popup doesn't work."
                                   id="ot1"/>
                </af:panelGroupLayout>
                
                <af:region value="#{bindings.taskflowemp1.regionModel}" id="r1"/>
                <af:region value="#{bindings.taskflowemp2.regionModel}" id="r2"/>
                
            </af:form>
        </af:document>
    </f:view>
</jsp:root>region.jsff
<?xml version='1.0' encoding='UTF-8'?>
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1" xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
          xmlns:f="http://java.sun.com/jsf/core">
<af:group id="g1">


       
    <af:group id="g2" binding="#{TestBean.popupGroup}">
      <af:popup childCreation="deferred" autoCancel="disabled" id="p1" binding="#{TestBean.testPopup}">
        
        <af:dialog id="d2" title="Dialog Title">
          <f:facet name="buttonBar"/>
          <af:outputText value="Dialog Contents" id="ot100"/>
        </af:dialog>
      </af:popup>
    </af:group>
    <af:panelGroupLayout id="pgl1">
      <af:panelBox text="Region" id="pb1">
        <f:facet name="toolbar"/>
        <af:commandButton text="showPopupBehavior" id="cb1" >
          <af:showPopupBehavior popupId="p1"/>
        </af:commandButton>
        <af:commandButton text="AdfPage.PAGE.findComponent JavaScript" id="cb2" actionListener="#{TestBean.popupTestJavaScript}"/>
        <af:commandButton text="RichPopup.Show() Java" id="cb3" actionListener="#{TestBean.popupTestJava}"/>
      </af:panelBox>
    </af:panelGroupLayout>
</af:group>
</jsp:root>TestBean.java
package view;
import javax.faces.context.FacesContext;
import javax.faces.event.ActionEvent;
import oracle.adf.view.rich.component.rich.RichPopup;
import org.apache.myfaces.trinidad.component.UIXGroup;
import org.apache.myfaces.trinidad.render.ExtendedRenderKitService;
import org.apache.myfaces.trinidad.util.Service;
public class TestBean {
    private RichPopup testPopup;
    private UIXGroup popupGroup;
    public TestBean() {
    public void setTestPopup(RichPopup testPopup) {
        this.testPopup = testPopup;
    public RichPopup getTestPopup() {
        return testPopup;
    public void popupTestJava(ActionEvent actionEvent) {
        if(testPopup != null){
            RichPopup.PopupHints ph = new RichPopup.PopupHints();
            testPopup.show(ph);
        }else{
            System.err.println("TestBean.testPopop IS NULL!");
    public void popupTestJavaScript(ActionEvent actionEvent) {
        showPopupTest("r1:0:p1");
    private static void showPopupTest(String popupId) {
        FacesContext facesContext = FacesContext.getCurrentInstance();
        ExtendedRenderKitService service =
            Service.getRenderKitService(facesContext,
                                        ExtendedRenderKitService.class);
        service.addScript(facesContext,
                          "AdfPage.PAGE.findComponent('" + popupId + "').show();");
    public void setPopupGroup(UIXGroup popupGroup) {
        this.popupGroup = popupGroup;
    public UIXGroup getPopupGroup() {
        return popupGroup;
}

Thanks that fixed the problem.
"a user error"
Well I followed your book! Chapter 6 of the "Oracle Fusion Developer Guide - Working with Bounded Task Flows in ADF Regions". I think this comes back to book writer error. I found almost no mention of BackingBeanScope in this chapter. Don't you think this would be an important note?
"did you know that there is a Java API (on the RichPopup instance) to launch a popup ?"
Yes I posted in my code! If you read the above code you would see it there.
I don't really understand why the scope of the bean has anything to do with af:showPopupBehavior or AdfPage.PAGE.findComponent.

Copy/paste report with a macro.

Hi all,
I want to know if a macro VBA able to copy/paste a report (the equivalent of report action --> Copy report / Paste report) exists ?
Thank you in advance.

Hi Fabrice,
with a button try
Sub Button1_Click()
Dim ws As Worksheet
Set ws = ThisWorkbook.Worksheets("Name of the Sheet You want to copy")
ws.Copy ThisWorkbook.Sheets(Sheets.Count)
End Sub
Regards
Roberto

KE31 - Copying a report with newly defined form

Hi ,
While creating a new profitability report(Report A) by copying an existing report (Report B with Form B) with the newly defined FORM(Form A) , the system is creating the new report(Report A) with the form (Form B) from the copied report.
How to create the report by copying another report (to get Report A with Form A)?
Thanks,
Prabha

Hi ,
Thanks for your reply.
I created form A and used KE31 for creating report A by copying report B.
While doing so, the report A got the form B not the form A. Though I assigned the form A while creating the report A (with copying report B), the report A got Form B.
How to create the report A with form A by copying report B?
Thanks,
Prabha

JRC bug: apostrophe in string parameter passed to Crystal Report with Command datasource to SQL Server

Post Author: nl11087
CA Forum: JAVA
A single quote/apostrophe in string parameter passed to a Crystal Report with Command datasource connecting to a SQL Server database, using sqljdbc driver does not escape the special character correctly. When doing a preview in the Crystal Reports IDE it allows you to escape the input parameter as expected and work correctly, but through the JRC component it fails. For string parameters without special sql server characters I experience no problems at all. When replacing the Command with a direct table there is also no problem.
Reproduction:
1. create a database db1, create a table table1 with a String type column col1.
2. Create new report Report1.rpt, create a connection to above, Add Command using 'SELECT col1, col2, col3 FROM table1 WHERE col1 = '{?Par1}' . Add a parameter field Par1 : String
3. In your java stand alone application using JRC add the parameter Par1 with a value "Jon Doe's Value" containing a single apostrophe. Export to PDF. (I also tried MSWord and this failed too, similar behavior). Additionally, in another test try to replaceAll("'","''") to escape it, preventing the code to break, but now it does not retrieve the expected row anymore and you end up with an empty report.
Exception StackTrace:
com.crystaldecisions.reports.exportinterface.exceptions.ExportException: JDBC Error: Incorrect syntax near 's'.
at com.crystaldecisions.reports.formatter.a.c.if(Unknown Source)
at com.crystaldecisions.reports.formatter.a.c.a(Unknown Source)
at com.businessobjects.reports.sdk.b.b.int(Unknown Source)
at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(Unknown Source)
at com.crystaldecisions.proxy.remoteagent.x.a(Unknown Source)
at com.crystaldecisions.proxy.remoteagent.q.a(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.dd.a(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.ReportSource.a(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.ReportSource.a(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.export(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.export(Unknown Source)
at com.crystaldecisions.reports.sdk.PrintOutputController.export(Unknown Source)
Caused by: com.crystaldecisions.reports.formatter.formatter.c: JDBC Error: Incorrect syntax near 's'.
at com.crystaldecisions.reports.formatter.formatter.objectformatter.bv.<init>(Unknown Source)
at com.crystaldecisions.reports.formatter.formatter.objectformatter.bv.if(Unknown Source)
at com.crystaldecisions.reports.formatter.formatter.e.l.<init>(Unknown Source)
at com.crystaldecisions.reports.formatter.formatter.e.p.<init>(Unknown Source)
at com.crystaldecisions.reports.formatter.formatter.e.p.a(Unknown Source)
at com.crystaldecisions.reports.formatter.a.c.a(Unknown Source)
... 17 more
Caused by: com.crystaldecisions.reports.dataengine.be: JDBC Error: Incorrect syntax near 's'.
at com.crystaldecisions.reports.dataengine.n.else(Unknown Source)
at com.crystaldecisions.reports.dataengine.n.nr(Unknown Source)
at com.crystaldecisions.reports.dataengine.n.bn(Unknown Source)
at com.crystaldecisions.reports.dataengine.n.bp(Unknown Source)
at com.crystaldecisions.reports.dataengine.n.else(Unknown Source)
at com.crystaldecisions.reports.dataengine.s.a(Unknown Source)
at com.crystaldecisions.reports.dataengine.bk.a(Unknown Source)
at com.crystaldecisions.reports.dataengine.bk.aa(Unknown Source)
at com.crystaldecisions.reports.dataengine.bk.<init>(Unknown Source)
at com.crystaldecisions.reports.dataengine.bk.<init>(Unknown Source)
at com.crystaldecisions.reports.dataengine.bk.<init>(Unknown Source)
at com.crystaldecisions.reports.dataengine.bk.a(Unknown Source)
... 23 more
Caused by: com.crystaldecisions.reports.reportdefinition.datainterface.n: JDBC Error: Incorrect syntax near 's'.
at com.crystaldecisions.reports.reportdefinition.datainterface.p.a(Unknown Source)
... 35 more
Caused by: com.crystaldecisions.reports.queryengine.driverImpl.m: JDBC Error: Incorrect syntax near 's'.
at com.crystaldecisions.reports.queryengine.driverImpl.o.eC(Unknown Source)
at com.crystaldecisions.reports.queryengine.driverImpl.o.if(Unknown Source)
at com.crystaldecisions.reports.queryengine.ap.ea(Unknown Source)
at com.crystaldecisions.reports.queryengine.ap.h(Unknown Source)
at com.crystaldecisions.reports.queryengine.ap.dV(Unknown Source)
at com.crystaldecisions.reports.queryengine.ax.if(Unknown Source)
at com.crystaldecisions.reports.queryengine.bc.if(Unknown Source)
at com.crystaldecisions.reports.queryengine.bc.do(Unknown Source)
at com.crystaldecisions.reports.queryengine.bc.do(Unknown Source)
at com.crystaldecisions.reports.queryengine.ae.cy(Unknown Source)
at com.crystaldecisions.reports.queryengine.ae.cz(Unknown Source)
at com.crystaldecisions.reports.queryengine.b1.bc(Unknown Source)
... 36 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 's'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement$StatementExecutionRequest.executeStatement(Unknown Source)
at com.microsoft.sqlserver.jdbc.CancelableRequest.execute(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeRequest(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source)
... 48 more
- JRCAgent3 detected an exception: An error occured while exporting the report
at com.businessobjects.reports.sdk.b.b.int(Unknown Source)
at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(Unknown Source)
at com.crystaldecisions.proxy.remoteagent.x.a(Unknown Source)
at com.crystaldecisions.proxy.remoteagent.q.a(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.dd.a(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.ReportSource.a(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.ReportSource.a(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.export(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.export(Unknown Source)
at com.crystaldecisions.reports.sdk.PrintOutputController.export(Unknown Source)

Post Author: nl11087
CA Forum: JAVA
A single quote/apostrophe in string parameter passed to a Crystal Report with Command datasource connecting to a SQL Server database, using sqljdbc driver does not escape the special character correctly. When doing a preview in the Crystal Reports IDE it allows you to escape the input parameter as expected and work correctly, but through the JRC component it fails. For string parameters without special sql server characters I experience no problems at all. When replacing the Command with a direct table there is also no problem.
Reproduction:
1. create a database db1, create a table table1 with a String type column col1.
2. Create new report Report1.rpt, create a connection to above, Add Command using 'SELECT col1, col2, col3 FROM table1 WHERE col1 = '{?Par1}' . Add a parameter field Par1 : String
3. In your java stand alone application using JRC add the parameter Par1 with a value "Jon Doe's Value" containing a single apostrophe. Export to PDF. (I also tried MSWord and this failed too, similar behavior). Additionally, in another test try to replaceAll("'","''") to escape it, preventing the code to break, but now it does not retrieve the expected row anymore and you end up with an empty report.
Exception StackTrace:
com.crystaldecisions.reports.exportinterface.exceptions.ExportException: JDBC Error: Incorrect syntax near 's'.
at com.crystaldecisions.reports.formatter.a.c.if(Unknown Source)
at com.crystaldecisions.reports.formatter.a.c.a(Unknown Source)
at com.businessobjects.reports.sdk.b.b.int(Unknown Source)
at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(Unknown Source)
at com.crystaldecisions.proxy.remoteagent.x.a(Unknown Source)
at com.crystaldecisions.proxy.remoteagent.q.a(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.dd.a(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.ReportSource.a(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.ReportSource.a(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.export(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.export(Unknown Source)
at com.crystaldecisions.reports.sdk.PrintOutputController.export(Unknown Source)
Caused by: com.crystaldecisions.reports.formatter.formatter.c: JDBC Error: Incorrect syntax near 's'.
at com.crystaldecisions.reports.formatter.formatter.objectformatter.bv.<init>(Unknown Source)
at com.crystaldecisions.reports.formatter.formatter.objectformatter.bv.if(Unknown Source)
at com.crystaldecisions.reports.formatter.formatter.e.l.<init>(Unknown Source)
at com.crystaldecisions.reports.formatter.formatter.e.p.<init>(Unknown Source)
at com.crystaldecisions.reports.formatter.formatter.e.p.a(Unknown Source)
at com.crystaldecisions.reports.formatter.a.c.a(Unknown Source)
... 17 more
Caused by: com.crystaldecisions.reports.dataengine.be: JDBC Error: Incorrect syntax near 's'.
at com.crystaldecisions.reports.dataengine.n.else(Unknown Source)
at com.crystaldecisions.reports.dataengine.n.nr(Unknown Source)
at com.crystaldecisions.reports.dataengine.n.bn(Unknown Source)
at com.crystaldecisions.reports.dataengine.n.bp(Unknown Source)
at com.crystaldecisions.reports.dataengine.n.else(Unknown Source)
at com.crystaldecisions.reports.dataengine.s.a(Unknown Source)
at com.crystaldecisions.reports.dataengine.bk.a(Unknown Source)
at com.crystaldecisions.reports.dataengine.bk.aa(Unknown Source)
at com.crystaldecisions.reports.dataengine.bk.<init>(Unknown Source)
at com.crystaldecisions.reports.dataengine.bk.<init>(Unknown Source)
at com.crystaldecisions.reports.dataengine.bk.<init>(Unknown Source)
at com.crystaldecisions.reports.dataengine.bk.a(Unknown Source)
... 23 more
Caused by: com.crystaldecisions.reports.reportdefinition.datainterface.n: JDBC Error: Incorrect syntax near 's'.
at com.crystaldecisions.reports.reportdefinition.datainterface.p.a(Unknown Source)
... 35 more
Caused by: com.crystaldecisions.reports.queryengine.driverImpl.m: JDBC Error: Incorrect syntax near 's'.
at com.crystaldecisions.reports.queryengine.driverImpl.o.eC(Unknown Source)
at com.crystaldecisions.reports.queryengine.driverImpl.o.if(Unknown Source)
at com.crystaldecisions.reports.queryengine.ap.ea(Unknown Source)
at com.crystaldecisions.reports.queryengine.ap.h(Unknown Source)
at com.crystaldecisions.reports.queryengine.ap.dV(Unknown Source)
at com.crystaldecisions.reports.queryengine.ax.if(Unknown Source)
at com.crystaldecisions.reports.queryengine.bc.if(Unknown Source)
at com.crystaldecisions.reports.queryengine.bc.do(Unknown Source)
at com.crystaldecisions.reports.queryengine.bc.do(Unknown Source)
at com.crystaldecisions.reports.queryengine.ae.cy(Unknown Source)
at com.crystaldecisions.reports.queryengine.ae.cz(Unknown Source)
at com.crystaldecisions.reports.queryengine.b1.bc(Unknown Source)
... 36 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near 's'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
at com.microsoft.sqlserver.jdbc.IOBuffer.processPackets(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement$StatementExecutionRequest.executeStatement(Unknown Source)
at com.microsoft.sqlserver.jdbc.CancelableRequest.execute(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeRequest(Unknown Source)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(Unknown Source)
... 48 more
- JRCAgent3 detected an exception: An error occured while exporting the report
at com.businessobjects.reports.sdk.b.b.int(Unknown Source)
at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(Unknown Source)
at com.crystaldecisions.proxy.remoteagent.x.a(Unknown Source)
at com.crystaldecisions.proxy.remoteagent.q.a(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.dd.a(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.ReportSource.a(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.ReportSource.a(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.export(Unknown Source)
at com.crystaldecisions.sdk.occa.report.application.PrintOutputController.export(Unknown Source)
at com.crystaldecisions.reports.sdk.PrintOutputController.export(Unknown Source)

Standard report with fixed position.

Hello,
I have a page where i want the first report to have a fixed position.
I have 3 regions with reports, the first will only display product name and number, the next report will display sales. The last report is very long so I have to scroll quite a bit. That's why i want the first report with names to have a fixed position so i can see which product i'm looking at.
I have tried to make a copy of the standard report template, and in the before rows i have this code
<table class="t3standard" summary="Report" style="position:fixed;">
this didn't work
Is this a way of making changes to the report template? Is it possible to make theese kind of changes in the report template or du I have to go inside the CSS file to add position:fixed somewhere?
Anders

What browser(s) are you using? Win IE doesn't support fixed positioning :-(
How about setting a fixed height for the last report and making it scrollable using overflow: scroll? This would make the first 2 reports "fixed" by default...

Issues with report with checkbox

Hi friends,
i have created a report with checkbox.
the query is
> select apex_item.checkbox(1,person_id,'unchecked') "select",
person_id,
AVAIL_SAL_CERTIFICATE,
OCCURANCE,
LAST_AVAILED_DATE,
REASON,
EFFECTIVE_START_DATE,
EFFECTIVE_END_DATE
from YY_SALARY_CERTIFICATEnow am having one button in my report region. suppose if i checked the particular row in report and clicked that button it should redirect to next page which is a form page it contains all the fields what report page had and it should display the value of corresponding report row which i checked.
how i can achevie this?
pls someone help me...

<li>On Submit PLSQL
DECLARE
lc_colln_name VARCHAr2(100) := 'MY_COLLN';
BEGIN
APEX_COLLECTION.CREATE_COLLECTION(lc_colln_name);
FOR i IN 1..APEX_APPLICATION.G_F01.COUNT --use the checkboxes array index used in query
LOOP
   --Add each checked record id to collection
   APEX_COLLECTION.ADD_MEMBER
            p_collection_name => lc_colln_name
           ,p_c001 => APEX_APPLICATION.G_F01(i) --Now c001 column of collection has this id
END LOOP;
END;<li>SQL Query of report in Page 2
select person_id,
AVAIL_SAL_CERTIFICATE,
OCCURANCE,
LAST_AVAILED_DATE,
REASON,
EFFECTIVE_START_DATE,
EFFECTIVE_END_DATE
from YY_SALARY_CERTIFICATE
         ,apex_collections AC
where AC.collection_name = 'MY_COLLN' --use the name of the collection created previously
AND    person_id = AC.c001

Multiple Reports In One Region - Question For Denes Kubicek

Denes,
I looked at what you've done on your demo app 31517, Page 152
(http://htmldb.oracle.com/pls/otn/f?p=31517:152), in which you place several reports in the same region. It is nicely done and a great example of something I
need to do at my work place.
I have two questions.
1) In your explanation link (takes me to your blog) you say you made changes to a copy of the Report Template and placed this copy into a copy of the Standard Page Template. However, I see that your reports are set to "No Template".
I've probably missed something here, but don't know what.
2) A more general question ... I'm intrigued in how you get tab item in, say, your Section 4 Tab Set (or any of the other Tab Sets) to "Stand Out" in bold letters
when clicked on. How are you doing this?
Thanks very much for your help. Yours is one of the great sites to learn from.
Elie

Apex v4. has parent and child regions (subregions) where child regions display inside the parent. If you make the child regions with no template, they will probably appear as if it's just two reports in one region.
Problem is, they display one above the other, not side by side. But there's been a recent thread on working around this just in the past few days on this forum.

Bug Appeal: LV6 activeX with Excel; Error -2147319784

At Thu, 16 Nov 2000 14:55:00
"Dominic Lavoie" wrote:
<-2147319784 Old format or invalid type library.
Dominic and others
This is an old bug in LabVIEW that I have been fighting
with for several years. The problem (as I have seen it) is that
LabVIEW for some reason on some PC's suddenly becomes unable to read
from the (NT-) registry that Excel is installed as an
available ActiveX component on the machine. In my case the
Excel8.olb file.
Under earlier verion of LabVIEW no error messages
was generated, but you could see the problem when entering
the list over ActiveX classes, Type library. Suddenly the Excel
would be gone from this list, and it will not come back no matter
how you try to install, reinstall or reconfigure the Excel (or Office)
system. (And the Regsvr32 program does not handle OLB files.)
The only way I have heard to fix it, is to reformat the
harddisk and install the OS and everything fresh. But you might
see the problem coming back again.
There might be a possibility that this bug is not NI's, but one
in the OS. When I use other programs to View/Edit the registry,
these programs have no problems of detecting the Excel library.
So I believe it is a LabVIEW bug !
When working with Excel and ActiveX with this problem
meant that you had to manually browse to the OLB file each time you
would want to work with it, or you would sometimes get messed up
the wires and VI's working against the Excel library.
Now, under LabVIEW 6i, this situation creates the error message
-2147319784, and the problem suddenly seems much bigger.
I have reported this bug two month ago to NI, together with some
other people that has seen the same problem. So far NI has not
been able to locate the problem in detail or done anything with it,
as far as I have been informed.
This has been a very frustrating experience for me, because there are
many other features under 6i that I would like to use right away.
But since I am working a lot with Excel as a data format from LabVIEW,
I cannot proceed with 6i before they have broken this bug.
So now I would like the LabVIEW community to help me push NI
a little in their effort to debug this one.
All questions of course assuming that you have installed Excel
on your PC.
Could as many as possible out there check out if,
when testing the ActiveX/Excel examples;
A) under 6i; do you get the Error -2147319784 ? (YES or NO)
B) under 5.1.1 or earlier; can you run the example Write Table to XL.vi ?
(YES or NO)
C) if B=NO, can you locate the Excel library in the ActiveX class list ?
(YES or NO)
D) Where in the world are you located (country) ?
(Some has speculated that this bug might be connected to a problem
with different OS versions in different parts of the world.)
E) What version of Excel are you using ?
F) What OS are you running ?
If you can't do both A and B/C, send me the one you can.
Please report your results directly to me.
DO NOT REPLY TO THIS LIST. I will send a
summary after a couple of weeks, to let you know
the results. And also if NI seems to make any progress here.
best regards
Martin Plassen

"[email protected]" wrote in message
news:[email protected]...
> Martin, I'm not sure how to reply directly to you. (I can't find your
> email address or anything.) I may be experiencing a very similar
> problem. I am trying to generate Excel reports using LabVIEW 6.0
> under a Windows 2000 OS. Under Win95 in LabVIEW 4 I had no problem
> but I recently updated. Now I can't even open Excel using the NI
> distributed LabVIEW 6i Excel toolkits from ni.com. When I execute the
> Open Excel vi I get a Windows error message, "Labview.exe has
> generated errors and will be closed by windows. An error log is being
> created." Could this be the same problem dominic was having under WIN
> NT?
dmbillings
It seems NI has been so kind as to remove the fix on this problem
from their Knowledgebase. Well, I dug up some old e-mails on the subject,
and here's one you should look through. According to NI this problem
should have been fixed under LV 6, so I really hope this is not what you are
facing...
Martin
Good news for all of you,
we have a bug-fix that seems to do the trick.
Here's the recipe , with my words:
Do You have the bug ?
You can confirm that the bug is there, by opening a new file in LabVIEW,
in the diagram, insert an Automation Open.VI, right-click on it,
Select ActiveX class, Browse, and check the Type Library list.
You should not see the Microsoft Excel5 and 8 library in the list,
if the bug is there.
As I have suspected for a long time, the whole bug was related to
how LabVIEW read the registry at startup to locate all ActiveX
components on the machine.
Here's the fix to try out;
1. Open the RegEdit program
2. Under HKEY_CLASSES_ROOT locate the TypeLib
3. Locate the Excel-key
On my machine this is {00020813-0000-0000-C000-000000000046}
(You will find it on top part, I think, not necessary to browse long
down.)
4. There are two base keys there, named "1.0" and "1.2".
Under the "1.0"-key, right-click and create new key, name it "0"
(zero).
5. Under the new "0"-key, create a new key kalled "win32".
6. Under the "1.0"-"9"-"win32" key you will find the link to the
Excel5-library on the machine, copy this link into the key you created
under pt 5.)
On my machine this is "C:\Program Files\Microsoft
Office\Office\XL5EN32.OLB".
That's all. Exit RegEdit.
Afterwards, check again that the Microsoft Excel5 and 8 libraries
is on the LabVIEW list mentioned above. After restarting LabVIEW of
course. It is not necessary to restart the PC.
Attached you wil find two gifs showing how this should look
in RegEdit before and after the described operation.
Good luck
PS: hacking around is the registry are do be done with
caution. The wrong actions here could have large consequences.
The two attached pictures should help you out,
but if you feel uncomfortable by working with the registry,
try to hook on to some hacker around that has been there before.
As I understand it, this is the reason that NI asked me also not to
give this info directly to the List-server. So please don't do it
you either. I plan to put the word out about the fix, not with these
details, but with a reference to the NI Knowledgebase that soon will
have this info.
You are welcome to send me a conformation that you see the
fix is working, or worst case, not.
Martin

How to create a report with dynamic columns

Hi all,
I am using Apex 4.0 with Oracle 10g
I am creating a report and I need to display columns dynamically based on the item values.
example:
I have a table employee with columns name, designation, sal
In the report page i have a select list with designations and when I select a designation from the select list,
I need to display the names of the employees horizontally,
like each name as a new column in the report with that particular designation. and same has to continue when I select different designations.
Can some one help me how we can do that.
I appreciate your answer
Thanks,
Rik

Essentially you want to write a pl/sql function which returns a varchar2 string. The contents of the string must be a valid sql statement.
Once you have done this, you need to add a report region as type sql report and you will have the option of writing it as a query or as a function returning query. Choose function returning query and enter in the function call.
Note your function must be valid, and must be executable by your apex parsing schema.
example:
create or replace
function test_report( p1_tablename in varchar2)
return varchar2
is
v_query varchar2(4000);
begin
v_query :=
'SELECT * from '||p_tablename;
return v_query;
end test_report;Edited by: Keith Jamieson on Aug 15, 2011 4:50 PM

Report with Checkbox

I am trying to follow the example shown at the below link but it is not working. I am modifying some of the code since I am using version 1.6. Any ideas as to what I may be doing wrong. The checkbox appears and I can select and deselect items but I cannot get P6_HOLDER to hold any of the values of the selected items. Thanks!
http://apex-smb.blogspot.com/2009/01/apex-report-with-checkboxes-advanced.html
First I created a page item called P6_HOLDER.
Next I created a report region (sequence 40) with the below code.
select htmldb_item.checkbox (1, dev_obj_id, 'onchange="spCheckChange(this);"',
:P6_HOLDER, ':') checkbox, dev_id, dev_obj_desc from edm_dev_obj where
dev_id = :P6_TEMP_DEV_ID
**I then created a html region (sequence 1) with the below code**
<SCRIPT src="http://www.google.com/jsapi"></SCRIPT>
<SCRIPT>
// Load jQuery
google.load("jquery", "1.2.6", {uncompressed:true});
function spCheckChange(pThis){
var get = new htmldb_Get(null,$v('pFlowId'),'APPLICATION_PROCESS=CHECKBOX_CHANGE',$v('pFlowStepId'));
get.addParam('f01',pThis.value); //Value that was checked
get.addParam('f02',pThis.checked ? 'Y':'N'); // Checked Flag
gReturn = get.get();
$f('checkListDisp').innerHTML=gReturn;
</SCRIPT>
CHECKBOX List:
<DIV id=checkListDisp>&P6_HOLDER.</DIV>
I then created an application process on Demand called CHECKBOX_CHANGE with the below code
DECLARE
v_item_val NUMBER := htmldb_application.g_f01;
v_checked_flag VARCHAR2 (1) := htmldb_application.g_f02;
BEGIN
IF v_checked_flag = 'Y' THEN
-- Add to the list
IF :P6_HOLDER IS NULL THEN
:P6_HOLDER := ':' || v_item_val || ':';
ELSE
:P6_HOLDER := :P6_HOLDER || v_item_val || ':';
END IF;
ELSE
-- Remove from the list
:P6_HOLDER := REPLACE (:P6_HOLDER, ':' || v_item_val || ':', ':');
END IF;
-- Just for testing
HTP.p (:P6_HOLDER);
END;

Hi
Create a page level validation (fucntion returning boolean) and write code similar to following
DECLARE
v_count NUMBER := 0;
BEGIN
FOR i IN 1..APEX_APPLICATION.G_F01.COUNT LOOP
IF APEX_APPLICATION.G_F01(i) IS NOT NULL THEN
v_count := v_count + 1;
END IF;
END LOOP;
IF v_count = 0 THEN
RETURN TRUE;
ELSE
RETURN FALSE;
END IF;
END;I take it your report query is similar to following
select apex_item.checkbox(1,"PK_CLMN") Tick, col2, col3 FROM tbl_nameCheers,
Hari

Bug in copying report with PLSQL region...

Similar Messages

Maybe you are looking for