Benjamin Intsiful on Oracle APEX

 Recently with the introduction of Apex 4.2 and later Apex 4.2.1 the default published  packaged applications comes with a sleek logo just at the left-hand corner of the the login screen. Fig 1 Fig 2 Fig 3 If u want to use these cool  sprites that come with the later releases as said in the the former. From the above diagram, looking into the css  inside the  i / or anywhere that your images are stored navigate to the cloud/app_theme/css/4_1.css You would find the img.appIcon.  class  which houses all the sprite launchpad logos in the Fig 1 Inside the css, locate ------App Icons Image-- img.appIcon.project_tracking{background-position:-256px 0}img.appIcon.solar{background-position:-320px 0}img.appIcon.website{background-position:-384px 0}img.appIcon.apex_service{background-position:-448px 0}img.appIcon.solar_red{background-position:-512px 0}img.appIcon.sales{background-position:-576px 0}img.appIcon.data_model...

Typically, after you have installed your  version of the  JasperReportsIntegration  toolkit on your Apache Tomcat J2EE server, the configuration files will be located in the directory  $CATALINA_HOME/ conf/Catalina/localhost/ JasperReportsIntegration.xml , for example version 4.7.0 of JasperReports, where  $CATALINA_HOME  represents the path to your installation of Tomcat where all the dataSource configuration are.  Similarly, after installation of your glassfish sever,  you would have to upload the .war file located in the toolkit version you download Eg. webapp\JasperReportsIntegration.war Locate  lib/ojdbc14 and lib/orai18n in the    JasperReportsIntegration  toolkit copy and   put them in {glassfish_installation}/glassfish/lib directory and restart glassfish (from {glassfish_installation}/glassfish/bin directory): asadmin stop-domain domain1 asadmin start-domain domain1 or If it was set as a service,...

Hi all, It's amazing when something new happens especially on the good side.I wanted to let you all know this blog is on the ODTUG Blog site. Go the ApexBlogroll and u should see it there  Benjamin Intsiful  . Thank You , HeatherKennedy Perry

On the 14. of december the APEX version 4.2.1.00.08 was released.  The Patchnotes are available under  APEX 4.2.1 Patchnotes . The fixed bugs are listed up  here . A short look over all fixed bugs sumerizes that the most fixes are belonging to the mobile theme and components of APEX. These Know Iusses are still open bugs: Developer Toolbar Not Available for Mobile Applications Page Submit Actions Not Working for Some Longer Mobile Select Lists Issues with Editing Items After Upgrade Theme 25 Alert Region Does Not Support Multiple Page Items in the Same Row Here are changes in the behaviour of APEX Maximum Width for Textareas Textarea can use less then maximum width Enhanced Security for Report Links JavaScript/jQuery can be mixed up with column name syntax javascript:alert( 'Delete # NAME #' ); jQuery Mobile updated to 1.2.0 AnyChart 6 AnyChart 6.0.11 is included Resizing of Charts on Mobile Page Now its possible to resize charts in the mobil...

Oracle has announced early adopters version of APEX release 4.2 @ https://apexea.oracle.com/pls/apex A whole host of new functionality has been added to APEX proving not only that Oracle is committed to pushing forward with APEX but also how great a tool it is. Some of the new functionality includes; Keep switches between Mobile and Desktop Applications  A faster application builder wizard allowing for simple applications to be built very quickly  Enhanced charting using both flash charting and HTML5 charts  Use of HTML5 page items with new item types such as sliders and additional attributes and  many many more features! The look and feel to the Application builder has also come on leaps and bounds and looks very impressive.  Enhanced Wizards Enhancements have also been made to the wizards allow for quicker generation of objects. Delivered with APEX 4.2 are the same applications available with the Oracle Cloud – these pre-built applicati...

DATE is the datatype that we are all familiar  with when we think about representing date and time values. It has the ability to store the month, day, year, century, hours, minutes, and seconds. It is typically good for representing data for when something has happened or should happen in the future.  The problem with the DATE datatype is its' granularity  when trying to determine a time interval between two events when the events happen within a second of each other. This issue is solved with the TIMESTAMP datatype. In order to represent the date stored in a more readable format, the TO_CHAR function has traditionally been wrapped around the date: SQL> SELECT  TO_CHAR(hiredate,'DD.MM.YYYY:HH24:MI:SS')  "hiredate"   FROM employees; hiredate ------------------- 17.12.1980:00:00:00 20.02.1981:00:00:00 The SYSDATE pseudo-column shows the current system date and time. Adding 1 to SYSDATE will advance the date by 1 day. Use fractions to add hours...

the  (+)  syntax is obsolete, proprietary syntax that Oracle used for years to accomplish the same results as an  OUTER JOIN . I assume they adopted their proprietary syntax before SQL-92 decided on the standard syntax. Using standard SQL  OUTER JOIN  syntax (which is now supported by all major RDBMS implementations) would be the following example : SELECT     Table1 . Category1 ,     Table1 . Category2 ,     COUNT (*) AS Total ,     COUNT ( Table2 . Stat ) AS Stat FROM Table1   LEFT OUTER JOIN Table2 ON ( Table1 . PrimaryKey = Table2 . ForeignKey ) GROUP BY Table1 . Category1 , Table1 . Category2 ; Which basically means - All rows from  Table1  are included in the query result. Where there are matching rows in  Table2 , include those rows (repeating content from  Table1  if there are multiple matching rows in  Table2 ). Where there are no matching rows ...