Hide the database connection window when load a report in a viewer control

When I load a report in viewer and the datasource is empty always appears a window for connect to database. How I can hide ALWAYS that window. Is possible? I did see some ways for do it, at before versions of CR, but seems don´t works in last version of Crystal Reports for .NET.
Anyway, is possible show a default text in viewer for information to user than don´t exists data?
Many thanks for the help, and excuse me my poor english.

The structure of XML is that: http://slexy.org/view/s20h0LVX1b
The XSD showed is used for the design of report.
In the empty datas the prompt dialog appears. The XML is different depend of context from application.
When I have the XML then load it in a DataSet object, and call the SetDataSource method from ReportDocument. In that moment ReportDocument don´t have any information over his state? Exists some way for know if will need extra information from user through the prompt dialog? In that case I could load another report with "NO DATA" text, but I don´t have info.
For example, is possible override the behavior from Crystal report viewer for show a different window? I did see events but nobody works for me.
Many thanks for the help and excuse me for my poor english.

Similar Messages

Multidimensional Connection Window When Using "New Report"

I have a PowerPivot workbook hosted in SharePoint PP gallery of two separate SharePoint installations. Using the PP Gallery capability "New Report", I can create a new Excel spreadsheet that uses this PowerPivot workbook as its data source. But
it only works on one SharePoint installation. On the other SharePoint installation, I get a "Multidimensional Connection" window I haven't seen before.
What is causing this window to come up, and what can be done to resolve this issue?
Thanks!

Weidong, is this still an issue?
Thanks!
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Bat file to hide the ms dos windows when running SWING component

Hi guys,
Could somebody tell me how to do the following?:
I want to create a .bat file which will be installed on my desktop, so that the swing jar file component is run, and open an application, but with the peculiarity that I don't want the MSDOS console open.
The best example about this, is Oracle Enterprise Manager, which is built on java and doesn't show any MSDOS (CMD) windows while executing.
Tx.

Correct.
Also note that if your code runs on multiple platforms, javaw is only on Windows.
Rob

When using the Database Connectivity Toolset, reads and writes with long binary fields are incompatible.

I am trying to write LabVIEW Variants to long binary fields in a .mdb file using the Database Connectivity Toolset. I get errors when trying to convert the field back to a variant after reading it back from the database.
I next tried flattening the variant before writing it and ultimately wound up doing the following experiments:
1) If I use DB Tools Insert Data to write an ordinary string and read it back using a DB Tools Select Data, the string is converted from ASCII to Unicode.
2) If I use DB Tools Create Parameterized Query to do an INSERT INTO or an UPDATE operation, specifying that the data is BINARY, then read it back using a DB Tools Select Data,
the length of the string is prepended to the string itself as a big-endian four-byte integer.
I can't think of any way to do a parameterized read, although the mechanism exists to return data via parameters.
Presuming that this same problem affects Variants when they are written to the database and read back, I could see why I get an error. At least with flattened strings I have the option of discarding the length bytes from the beginning of the string.
Am I missing something here?

David,
You've missed the point. When a data item is flattened to a string, the first four bytes of the string are expected to be the total length of the string in big-endian binary format. What is happening here is that preceding this four-byte length code is another copy of the same four bytes. If an ordinary string, "abcdefg" is used in place of the flattened data item, it will come back as <00><00><00><07>abcdefg. Here I've used to represent a byte in hexadecimal notation. This problem has nothing to do with flattening and unflattening data items. It has only to do with the data channel consisting of writing to and reading from the database.
I am attaching three files that you can use to demonstrate the problem. The VI file c
ontains an explanation of the problem and instructions for installing and operating the demonstration.
Ron Martin
Attachments:
TestLongBinaryFields.vi ‏132 KB
Sample.UDL ‏1 KB
Sample.mdb ‏120 KB

Database connection problem when i try store the values in JTable

Hi Sir,
I have a database connection problem when i try to store the data's in a JTable.I think the problem is with in the database connection.I have used 3 vectors here.The database which i have used is
Access.Where the program is compiling well.But when i run it only the first column heading is printed and error message showing that
"Invalid Cursor State".I need to solve this problem.pls. do help me.
I will provide u with the code.
import java.awt.*;
import java.awt.event.*;
import javax.swing.*;
import javax.swing.event.*;
import java.util.*;
import java.sql.*;
public class DataBaseVector extends JPanel
//Container contentPane=getContentPane();
JScrollBar jsb = new JScrollBar(JScrollBar.HORIZONTAL);
JScrollBar jsb1 = new JScrollBar(JScrollBar.VERTICAL);
Image i1;
String url="jdbc:odbc:Ananth";
Vector col=new Vector();
Vector rows=new Vector();
Vector rdata=new Vector();
Connection conn;
public DataBaseVector()
//super("JTable With ScrollBars");
this.setLayout(new BorderLayout());
UIManager.put("ScrollBar.track",Color.red);
UIManager.put("ScrollBar.thumb",Color.blue);
try
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
conn=DriverManager.getConnection(url); // Is there any problem here?
Statement st=conn.createStatement();
ResultSet rs=st.executeQuery("Select * from AccountMaster");
// rs is the result set obtained
ResultSetMetaData rsmd=rs.getMetaData();
int cols=rsmd.getColumnCount();
for(int i=1;i<=cols;i++)
col.addElement(rsmd.getColumnName(i));
rdata.addElement(rs.getString(i));
rows.addElement(rdata);
}catch(Exception e)
     System.out.println("The Error Message was:"+e.getMessage());
JTable jt=new JTable(rows,col);
int v=ScrollPaneConstants.VERTICAL_SCROLLBAR_AS_NEEDED;
int h=ScrollPaneConstants.HORIZONTAL_SCROLLBAR_AS_NEEDED;
JScrollPane jsp=new JScrollPane(jt,v,h);
this.add(jsp,BorderLayout.CENTER);
this.add(jsb, BorderLayout.SOUTH);
this.add(jsb1, BorderLayout.EAST);
public static void main(String args[])
JFrame jf=new JFrame();
JPanel frame=new DataBaseVector();
jf.getContentPane().add(frame);
jf.setSize(800,600);
jf.setVisible(true);
Thanx,
m.ananthu

The problem is ResultSet.next() is not called.
Try this and modify the table creation as you need.
ResultSetMetaData rsmd=rs.getMetaData();
int cols=rsmd.getColumnCount();
     while(rs.next()) {
          for(int i=1;i<=cols;i++)
                    col.addElement(rsmd.getColumnName(i));
                    rdata.addElement(rs.getString(i));
          rows.addElement(rdata);
Hope this helps

Workspace Error 8001: The Database Connection could not be found

We had to reboot all our windows servers recently and since then all the database connections in the database base manager in workspace are gone.
I can see all the existing reports but cannot use any of them as I dont have any connections.
Also I cannot create any new connections
I get the error 8001: The Database Connection could not be found: 13cbd63_12b5e2a8b73_-7f8f when I try to create a new connection.
Not sure what the problem is.
Any suggestions?

Hi Pat,
It loks like your Biplus relational DB is corrupted, try with those steps:
1. De-register BI+ from Shared Services (Config Utility->Hyperion Reporting and Analysis > Deregister from Shared Services)
2. Configure against the backup database (Drop and recreate tables option).
3. Re-register BI+ with Shared Services.
4. Re-deploy BI+.
5. Test Workspace and add new connections.
Regards.

Error while applying a patch "Unable to get the database connection"

Dear Experts,
A patch which got successfully applied is failing Production and the error is kind of surprising to me.
Apps version is 11.5.10.2
db version is 10.2.0.4
The worker log file shows
Time when worker restarted job: Thu Nov 24 2011 22:14:52
Start time for file is: Thu Nov 24 2011 22:14:52
adjava -ms128m -mx256m -nojit oracle.apps.fnd.odf2.FndXdfCmp &un_apps &pw_apps &un_apps &pw_apps &jdbc_protocol &jdbc_db_addr table &fullpath_pa_patch/115
Reading product information from file...
Reading language and territory information from file...
Reading language information from applUS.txt ...
Temporarily resetting CLASSPATH to:
"/erp/oracle/prodappl/ad/11.5.0/java/adjri.zip:/usr/java14/jre/lib/charsets.jar:/usr/java14/jre/lib/core.jar:/usr/java14/jre/lib/graphics.jar:/usr/java1
Calling /usr/java14/bin/java ...
Exception occured
              Copyright (c) 2003 Oracle Corporation
                 Redwood Shores, California, USA
         XDF(XML Object Description File) Comparison Utility
                        Version 1
NOTE: You may not use this utility for custom development
      unless you have written permission from Oracle Corporation.
Unable to get the database connection using schema username/passwordIo exception: The Network Adapter could not establish the connection
AD Run Java Command is complete.
                     Copyright (c) 2002 Oracle Corporation
                        Redwood Shores, California, USA
                                    AD Java
                                 Version 11.5.0
NOTE: You may not use this utility for custom development
      unless you have written permission from Oracle Corporation.
AD Worker error:
The above program failed. See the error messages listed
above, if any, or see the log and output files for the program.
Time when worker failed: Thu Nov 24 2011 22:14:53
{code}
The error says database connection error. I am able to connect to the database using sqlplus. I tried to restart the failed worker, but the same error is repeating.
Any help would be appreciated.
Thanks
qARS
Edited by: user7640966 on Nov 24, 2011 9:07 AM

Hussein,
One thing which I noticed now is in the apps Tier the
tnsnames.ora under $TNS_ADMIN
shows entry like this:
PROD=
        (DESCRIPTION=
                (ADDRESS=(PROTOCOL=tcp)(HOST=<appsServerName>)(PORT=1521))
                (ADDRESS=(PROTOCOL=tcp)(HOST=<dbServer>)(PORT=1521))
            (CONNECT_DATA=
                (SID=PROD)
        )Actually *(ADDRESS=(PROTOCOL=tcp)(HOST=<appsIPaddress>)(PORT=1521))* this line in the tnsnames.ora is not correct. In fact the appsServerName should be replaced with dbServerName
I deleted the tnsnames.ora and reran autoconfig but it is again recreating the same entry.
Any clue how this can be fixed?
Thanks
qARS

Why do I get a class conflict between the Prepare SQL.vi and the Get Column Name.vi with the SQL Toolkit compatibility vis from the Database Connectivity Toolkit?

I have done extensive programming with the SQL Toolkit with LabVIEW versions through 6.1. My customer now wants to upgrade to Windows 7, so I am trying to upgrade to LabVIEW 2009 (my latest purchased version) using the Database Connectivity Toolkit, and the SQL Toolkit Compatibility vis. Everything seemed to be going okay with the higher level SQL operations, but I ran into trouble with the Get Column Name.vi.
The pictures below show the problem. The original SQL Toolkit connected the Prepare SQL.vi with the Get Column Name.vi with a cluster of two references, one for connection, and one for sql. The new compatibility vis have a class conflict in the wire because the Prepare SQL.vi contains a cluster with connection, and command references, but the Get Column Name.vi expects a cluster with connection and recordset references.
How do I resolve this conflict?
Thank You.
Dan

I've never worked with the old version of the toolkit, so I don't know how it did things, but looking inside the SQL prep VI, it only generates a command, and the the column name VI wants a recordset. I'm not super familiar with all the internals of ADO, but my understanding is that is standard - you only have the columns after you execute the command and get the recordset back. What you can apparently do here is insert the Execute Prepared SQL VI in the middle and that will return what you need.
I'm not sure why it worked before. Maybe the execute was hidden inside the prep VI or maybe you can get the column names out of the command object before execution. In general, I would recommend considering switching to the newer VIs.
Try to take over the world!

Problem in getting the database connection from a connection pool

Hai All,
I am facing a problem in getting the database connection from a connection pool created on weblogic server 8.1.
I am using the Oracle database 8.1.7.
I have configured my connection pool, datasource and JNDI in weblogic.
In my java program i have the following code to retrieve the connection.
import java.sql.*;
import java.util.Hashtable;
import javax.naming.Context;
import javax.naming.InitialContext;
class jdbcshp1 {
    public static void main(String[] args) {
     Connection connection = null;
     try {
           Hashtable ht = new Hashtable();
           ht.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory"); // Wanna get rid of this.
           ht.put(Context.PROVIDER_URL,"t3://localhost:7001"); // wanna get rid of this.
           // Get a context for the JNDI look up
           Context ctx = new InitialContext(ht);
        javax.sql.DataSource ds = (javax.sql.DataSource) ctx.lookup ("myjndi1");
          //Create a connection object
          connection = ds.getConnection();
     The above code is working fine but, the two ht.put statements are creating problem.
The problem is, after converting the application into WAR file it can be deployed
on any machine or different port on same machine. My application fails if its deployed on
weglogicserver which is at different port.
Is there any way that i can get rid of those ht.put statements or any other way to solve the problem.
any help is appreciated.
Thanks in advance
Pooja.

Hai All,
Firstly, thanks for ur reply.
Even i have seen some code which uses context constructor with out any parameter and works fine.
i dont understand why its not working for my code.
When i remove those ht.put code and use context constructor with out any parameter, it giving an error.
Context ctx = new InitialContext();
javax.sql.DataSource ds = (javax.sql.DataSource) ctx.lookup ("ocjndi");
connection = ds.getConnection();The error is as follows:
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
the above error is forcing me to include those code but if the port number is changed the code will not work. Plz let meknow if some setting have to be made.
I appreciate all ur valuable help.
Thanks once again.
Pooja.

How to hide Database Logon option when scheduling Crystal Report in BOE?

Hi All,
For security reason, we are try to hide the Database Logon option in Crystal Report Schedule page in InfoView.
There is option in CMC which we can configure the default Database logon option so that users do not have to enter the logon everytime they view or schedule the report. However, we are looking to hide this option completely.
Does anyone know if there is a security setting which can hide the option from specific users?
Thanks,
Bobby

Hi Bobby,
As Jorge informed that there is no method available within CMC to hide database logon option when scheduling or viewing a Crystal Report in the Info view. This is very much true.
But as you also mentioned that you don't want your users to enter the database logon credentials evertime they view or schedule a crystal report, there is one setting in CMC which we can do to avoid prompt for database logon credentials.
CMC - Home - Go to that specific crystal report - Click Process tab - Click the sub-tab 'Database' and at the bottom of the page there is an option "Use same database logon as when report is run". Check this option after providing the database credentials and click UPDATE.
Now whenever users try to view or schedule this specifc crystal report they won't be prompted for the database logon credentials.
Regards,
Venkat

Database login windows when using DataSet ( CR2008 )

After executing this code, I get a database login window when using a DataSet, wondering why I am asked for user/pwd when using DataSets.

Thanks Jonathan for the tip. I tried it before and after the setDatabaseLogin call yesterday, but got the same results. I'm still going to follow your suggestion because that makes more sense.
Turns out it was the configuration of my ODBC/System DSN that was causing the problem. I reconfigured the System DSN by clearing the check box to provide username/password and now I don't get the Database Login anymore.
I found a different blog post that answered the OLE DB issue I was seeing where the DatabaseName was coming up blank:
Login Error Database at Runtime
Haven't tried it yet and probably won't because I got the Viewer to work with ODBC the way I like it.
Thanks for the help!

How to hide the fields with labels when page re-rendering

Hi Gurus,
Please help me to hide the fields with labels when page is re-rendered.
I have written a on load : before process also.
But it is not working
Thanks in advance
kavitha L

Hi jari and Bruce,
Thanks for your reply. I am sorry that, i am not clear
I have a javascript like
function showcase()
   var ctry = document.getElementById('P3_CHANNEL').value;
   if(ctry == 'Affiliate') {
    $x_Hide('P3_PUBLLICATION');
    $x_Hide('P3_PUBLLICATION_label');
    $x_Hide('P3_CIRCULATION');
    $x_Hide('P3_CIRCULATION_label');
    $x_Hide('P3_MEDIA_CPM');
    $x_Hide('P3_MEDIA_CPM_label');
    $x_Hide('P3_RATE_CARD');
    $x_Hide('P3_RATE_CARD_label');
    $x_Hide('P3_DISCOUNT');
    $x_Hide('P3_DISCOUNT_label');
    $x_Hide('P3_CTYPE');
    $x_Hide('P3_CTYPE_label');
    $x_Hide('P3_DAREA');
    $x_Hide('P3_DAREA_label');
    $x_Hide('P3_CREATIVE');
    $x_Hide('P3_CREATIVE_label');
    $x_Hide('P3_COLOR_TONE');
    $x_Hide('P3_COLOR_TONE_label');
    $x_Hide('P3_SIZE');
    $x_Hide('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if(ctry == 'Direct Mail')
    { $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Show('P3_CTYPE');
    $x_Show('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Show('P3_CREATIVE');
    $x_Show('P3_CREATIVE_label');
    $x_Show('P3_COLOR_TONE');
    $x_Show('P3_COLOR_TONE_label');
    $x_Show('P3_SIZE');
    $x_Show('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if(ctry == 'E-Mail')
    { $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Show('P3_CTYPE');
    $x_Show('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Show('P3_CREATIVE');
    $x_Show('P3_CREATIVE_label');
    $x_Show('P3_COLOR_TONE');
    $x_Show('P3_COLOR_TONE_label');
    $x_Hide('P3_SIZE');
    $x_Hide('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if((ctry == 'Online') || (ctry == 'PPC'))
    { $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Hide('P3_CTYPE');
    $x_Hide('P3_CTYPE_label');
    $x_Hide('P3_DAREA');
    $x_Hide('P3_DAREA_label');
    $x_Hide('P3_CREATIVE');
    $x_Hide('P3_CREATIVE_label');
    $x_Hide('P3_COLOR_TONE');
    $x_Hide('P3_COLOR_TONE_label');
    $x_Hide('P3_SIZE');
    $x_Hide('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if(ctry == 'Outdoor')
    { $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Hide('P3_CTYPE');
    $x_Hide('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Show('P3_CREATIVE');
    $x_Show('P3_CREATIVE_label');
    $x_Hide('P3_COLOR_TONE');
    $x_Hide('P3_COLOR_TONE_label');
    $x_Hide('P3_SIZE');
    $x_Hide('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if(ctry == 'PR')
    { $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Hide('P3_CTYPE');
    $x_Hide('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Hide('P3_CREATIVE');
    $x_Hide('P3_CREATIVE_label');
    $x_Hide('P3_COLOR_TONE');
    $x_Hide('P3_COLOR_TONE_label');
    $x_Hide('P3_SIZE');
    $x_Hide('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if(ctry == 'Radio')
    { $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Show('P3_CTYPE');
    $x_Show('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Hide('P3_CREATIVE');
    $x_Hide('P3_CREATIVE_label');
    $x_Hide('P3_COLOR_TONE');
    $x_Hide('P3_COLOR_TONE_label');
    $x_Show('P3_SIZE');
    $x_Show('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if(ctry == 'TV')
    { $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Show('P3_CTYPE');
    $x_Show('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Show('P3_CREATIVE');
    $x_Show('P3_CREATIVE_label');
    $x_Hide('P3_COLOR_TONE');
    $x_Hide('P3_COLOR_TONE_label');
    $x_Show('P3_SIZE');
    $x_Show('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if(ctry == 'A')
    { $x_Show('P3_POSITION');
    $x_Show('P3_POSITION_label');
   $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Show('P3_CTYPE');
    $x_Show('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Show('P3_CREATIVE');
    $x_Show('P3_CREATIVE_label');
    $x_Show('P3_COLOR_TONE');
    $x_Show('P3_COLOR_TONE_label');
    $x_Show('P3_SIZE');
    $x_Show('P3_SIZE_label');
    html_ShowItemRow('P3_ISSUE_DT');
else if(ctry == 'Print')
   $x_Show('P3_POSITION');
    $x_Show('P3_POSITION_label');
   $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Show('P3_CTYPE');
    $x_Show('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Show('P3_CREATIVE');
    $x_Show('P3_CREATIVE_label');
    $x_Show('P3_COLOR_TONE');
    $x_Show('P3_COLOR_TONE_label');
    $x_Show('P3_SIZE');
    $x_Show('P3_SIZE_label');
    html_ShowItemRow('P3_ISSUE_DT');
   doSubmit('CREATE');
function showcase12()
   var ctry = document.getElementById('P3_CHANNEL').value;
   if(ctry == 'Affiliate') {
    $x_Hide('P3_PUBLLICATION');
    $x_Hide('P3_PUBLLICATION_label');
    $x_Hide('P3_CIRCULATION');
    $x_Hide('P3_CIRCULATION_label');
    $x_Hide('P3_MEDIA_CPM');
    $x_Hide('P3_MEDIA_CPM_label');
    $x_Hide('P3_RATE_CARD');
    $x_Hide('P3_RATE_CARD_label');
    $x_Hide('P3_DISCOUNT');
    $x_Hide('P3_DISCOUNT_label');
    $x_Hide('P3_CTYPE');
    $x_Hide('P3_CTYPE_label');
    $x_Hide('P3_DAREA');
    $x_Hide('P3_DAREA_label');
    $x_Hide('P3_CREATIVE');
    $x_Hide('P3_CREATIVE_label');
    $x_Hide('P3_COLOR_TONE');
    $x_Hide('P3_COLOR_TONE_label');
    $x_Hide('P3_SIZE');
    $x_Hide('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if(ctry == 'Direct Mail')
    { $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Show('P3_CTYPE');
    $x_Show('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Show('P3_CREATIVE');
    $x_Show('P3_CREATIVE_label');
    $x_Show('P3_COLOR_TONE');
    $x_Show('P3_COLOR_TONE_label');
    $x_Show('P3_SIZE');
    $x_Show('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if(ctry == 'E-Mail')
    { $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Show('P3_CTYPE');
    $x_Show('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Show('P3_CREATIVE');
    $x_Show('P3_CREATIVE_label');
    $x_Show('P3_COLOR_TONE');
    $x_Show('P3_COLOR_TONE_label');
    $x_Hide('P3_SIZE');
    $x_Hide('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if(ctry == 'Event')
    { $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Show('P3_CTYPE');
    $x_Show('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Hide('P3_CREATIVE');
    $x_Hide('P3_CREATIVE_label');
    $x_Hide('P3_COLOR_TONE');
    $x_Hide('P3_COLOR_TONE_label');
    $x_Hide('P3_SIZE');
    $x_Hide('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if(ctry == 'Other')
    { $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Show('P3_CTYPE');
    $x_Show('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Show('P3_CREATIVE');
    $x_Show('P3_CREATIVE_label');
    $x_Hide('P3_COLOR_TONE');
    $x_Hide('P3_COLOR_TONE_label');
    $x_Hide('P3_SIZE');
    $x_Hide('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if((ctry == 'Online') || (ctry == 'PPC'))
    { $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Hide('P3_CTYPE');
    $x_Hide('P3_CTYPE_label');
    $x_Hide('P3_DAREA');
    $x_Hide('P3_DAREA_label');
    $x_Hide('P3_CREATIVE');
    $x_Hide('P3_CREATIVE_label');
    $x_Hide('P3_COLOR_TONE');
    $x_Hide('P3_COLOR_TONE_label');
    $x_Hide('P3_SIZE');
    $x_Hide('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if(ctry == 'Outdoor')
    { $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Hide('P3_CTYPE');
    $x_Hide('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Show('P3_CREATIVE');
    $x_Show('P3_CREATIVE_label');
    $x_Hide('P3_COLOR_TONE');
    $x_Hide('P3_COLOR_TONE_label');
    $x_Hide('P3_SIZE');
    $x_Hide('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if(ctry == 'PR')
    { $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Hide('P3_CTYPE');
    $x_Hide('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Hide('P3_CREATIVE');
    $x_Hide('P3_CREATIVE_label');
    $x_Hide('P3_COLOR_TONE');
    $x_Hide('P3_COLOR_TONE_label');
    $x_Hide('P3_SIZE');
    $x_Hide('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if(ctry == 'Radio')
    { $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Show('P3_CTYPE');
    $x_Show('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Hide('P3_CREATIVE');
    $x_Hide('P3_CREATIVE_label');
    $x_Hide('P3_COLOR_TONE');
    $x_Hide('P3_COLOR_TONE_label');
    $x_Show('P3_SIZE');
    $x_Show('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if(ctry == 'TV')
    { $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Show('P3_CTYPE');
    $x_Show('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Show('P3_CREATIVE');
    $x_Show('P3_CREATIVE_label');
    $x_Hide('P3_COLOR_TONE');
    $x_Hide('P3_COLOR_TONE_label');
    $x_Show('P3_SIZE');
    $x_Show('P3_SIZE_label');
    $x_Hide('P3_POSITION');
    $x_Hide('P3_POSITION_label');
   html_HideItemRow('P3_ISSUE_DT');
else if(ctry == 'A')
    { $x_Show('P3_POSITION');
    $x_Show('P3_POSITION_label');
   $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Show('P3_CTYPE');
    $x_Show('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Show('P3_CREATIVE');
    $x_Show('P3_CREATIVE_label');
    $x_Show('P3_COLOR_TONE');
    $x_Show('P3_COLOR_TONE_label');
    $x_Show('P3_SIZE');
    $x_Show('P3_SIZE_label');
    html_ShowItemRow('P3_ISSUE_DT');
else if(ctry == 'Print')
   $x_Show('P3_POSITION');
    $x_Show('P3_POSITION_label');
   $x_Show('P3_PUBLLICATION');
    $x_Show('P3_PUBLLICATION_label');
    $x_Show('P3_CIRCULATION');
    $x_Show('P3_CIRCULATION_label');
    $x_Show('P3_MEDIA_CPM');
    $x_Show('P3_MEDIA_CPM_label');
    $x_Show('P3_RATE_CARD');
    $x_Show('P3_RATE_CARD_label');
    $x_Show('P3_DISCOUNT');
    $x_Show('P3_DISCOUNT_label');
    $x_Show('P3_CTYPE');
    $x_Show('P3_CTYPE_label');
    $x_Show('P3_DAREA');
    $x_Show('P3_DAREA_label');
    $x_Show('P3_CREATIVE');
    $x_Show('P3_CREATIVE_label');
    $x_Show('P3_COLOR_TONE');
    $x_Show('P3_COLOR_TONE_label');
    $x_Show('P3_SIZE');
    $x_Show('P3_SIZE_label');
    html_ShowItemRow('P3_ISSUE_DT');
}This script i am calling on, onchange() for the select list item P3_CHANNEL and it is working fine.
But i have a create button and cancel button.
After filling the details in the required columns, when i click the create button, if any validation errors are there.. the page is re-rendered. while doing that the hidden items are getting displayed back.
Tried Solutions:
1. I created a same function once more and in the last added the doSubmit('CREATE') and called the script from the create button.
At that time the hidden fields labels are getting displayed.
2. I created a process On load before header To call this script on a condition :REQUEST = 'CREATE'
Then also fruitless..
I hope now it is clear....
Please! Any suggestion are mostly appreciated.
Thanks in advance
Kavitha L

Database connection error when running report from web application

Hi all,
When I open a report in Reports Builder , and enter the database connection parameters, everything works fine. When I run my web application from JDeveloper (9.0.5.1), and I tried to run a report, I get this error:
Rep-501 : Unable to connect to the specified database.
I have ran tnsping, and it works fine. My tnsnames.ora file looks like this :
GPGWL =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1522))
(CONNECT_DATA =
(SERVICE_NAME = GPGWL)
)

Please ask this question in Jdeveloper forum.

Timeout: Tuxedo kills the service but not the database connection

Hi all,
I am experiencing some performance problems on my system due an efficient SQL and a Tuxedo improper timeout handling.
A service is using a "problematic" SQL (we will tune it but it's not the main problem). After 60 seconds from the execution, Tuxido kills the services for a timeout.
At this point I would like Tuxedo to notify DB2 database as well in order to stop processing the SQL. Instead the SQL continues running on the database (also if the service is killed) and this produce a gradual slow down of the performances.
In the UBBCONFIG, we are using a service configuration like the following timeout configuration:
.RESOURCES
SCANUINIT 5
SANITYSCAN 6
BLOCKTIME 12
.SERVICES
DEFAULT: SVCTIMEOUT=45
service1 SVCTIMEOUT=60 TRANTIME=60
service2 SVCTIMEOUT=60 TRANTIME=60
Note: not all the services are listed in the .SERVICES section and we are using the default NOTIFY as well as an OPENINFO.
Can you please help me in finding a configuration to kill both the services and the database?
Thanks in advance,
Benedetto

Hi Benedetto.
First of all, Tuxedo doesn't kill services, it kills servers. Your UBBCONFIG file specifies three timeouts, BLOCKTIME, SVCTIMEOUT, and TRANTIME.
BLOCKTIME specifies how long a Tuxedo API that needs a response will wait for that response. If the response isn't received in that period of time, Tuxedo will return TPETIME to the caller. As with any failure, if the request was part of a transaction, the transaction is marked rollback only. Note, this timeout does not affect the request, whether sitting in a server's IPC queue or currently executing in a server.
SVCTIMEOUT is a much more severe timeout and determines how long Tuxedo will allow a service implementation to execute. If a service implementation doesn't reply within the SVCTIMEOUT period, Tuxedo will issue an OS level KILL request to kill the process. If the server is marked restartable, Tuxedo will then try to restart the server assuming none of the restart limits have been reached. Killing the server causes the request to be lost within the server so the caller will stay blocked until BLOCKTIME is reached at which point the above actions will take place.
TRANTIME is the amount of time Tuxedo allows a transaction to remain active and viable. When this period expires, Tuxedo will mark the transaction as timed out with the only option being rollback. As well, Tuxedo aborts any API requests that would normally cause messaging to occur, i.e., making a tpcall() within a timed out transaction will fail without any attempt to call the service.
So in your case, the issue is partially that you have the values of your timeouts in somewhat reverse order. Typically we see BLOCKTIME being the smallest value, with TRANTIME typically larger than BLOCKTIME, and SVCTIMEOUT larger even still, although there are good reasons for exceptions to this guideline. Part of the reasoning behind this is that killing a server is a significant thing and its usually best to try and let the server complete whatever its doing, if if the work has been timed out either due to BLOCKTIME or TRANTIME, since the cost of killing and restarting a server is significant.
Tuxedo will notify the database of the transaction status when the application finally issues a tpcommit() or a tpabort() request, but not until then. Although, if SVCTIMEOUT is hit, then killing the server should cause the database connection to be lot.
If you could describe the behavior you are seeing and the relevant portions of your ULOG we can try to make some sense of what is happening.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

If the database is shutdown when the applcation is running what is happened

I am using coneection pool to connect database. If the database is shutdown when the applcation is running what is happened? and how the database will be reconnected.
I am using MySQL 3.23.52, Tomcat 4.1.12

Hi,
Performance of any n-tier system which takes the advantage of connection pooling will be much higher compared to its non-pooled counterpart.
You have to be very careful while designing/using a connection pool.if u are using pool obtained from a third party,ur control on this pool will be limited - with a few set/get methods.
A well designed pool wont create much trouble. if u are creating your own pool, basic steps required are
1.create 'n' number of connections
2.whenever user requests for a connection, check the validity of the connection- by sendin a simple select query etc- and if its not stale,give this connection to the caller.
3.if the connection is stale ie it fails the pretest, close all the connections and create the pool afresh.
4.connections obtained from the pool will be automatically returned back to the pool whenever the applciation call conn.close().
from ur application, follow the steps for each connection you use (not necessary for a well designed pool)
1.call ds.getconnection()
2.check validity of this connection by sending a simple select query.if it works,everything is fine. otherwise something is wrong with connection(not always).
3.sql exception may occur during the execution of sql query. this can be due to either
a.database shut down (network related)
b.database specific - like wrong query,invalid objects etc
you have to look at the sql state/vendor code (which can be retrieved from the caught exception). the retrieved code will give you a hint why the error (network or database specific).and you can act accordingly.
Most of the app servers comes with builtin connection pooling module. and handling stale connection is not a difficult task for the programmer. eg: if you are designing applcations for IBM websphere, you can use StaleConnectionException in your code.if this exception is caught,the whole pool is destroyed and created afresh.
HTH,
-asharafkk

Hide the database connection window when load a report in a viewer control

Similar Messages

Maybe you are looking for