Creating dimension LEVEL with a VIEW

Hello.
Because we don't have lots of HDD space we have created 5 views. (using some DBLINKS)
4 to dimension tables
1 to a fact table
When I try to create a level in a new dimension (OEM) using the WIZARD, for instance, I have to select a TABLE and select the attribute I want.
Can I use the VIEW instead of a TABLE??
Thanks
Peter

Using the CWM1 views through Enterprise Manager Dimensions/Lookups must be TABLES, fact tables can be VIEWS
In the CWM2 set up you can utilise VIEWS for all componenets. Furthermore, my data mart has a distributed environment where reference data is physically located in a remote database.
In order to reference the remote tables I have considered database synonyms, but this did not work.
Secondly, we created a number of views containing DBLINKS to the remote database. This works but performance can be poor because the SQL generated by the BI Beans, makes several calls to the complex view to create hierarchies, retrieve selections etc. which can be inefficient.
I think my next steps will be to create Materialized views on the data mart from the remote reference database.
Finally, run the following statement before your CWM2 statements. cwm2_olap_manager.Set_Echo_ON will provide a complete output from your statements rather than just "Procedure Completed Sucessfully"
SET ECHO ON
SET LINESIZE 120
SET PAGESIZE 50
SET SERVEROUTPUT ON
execute cwm2_olap_manager.Set_Echo_ON;

Similar Messages

  • Create Dimension Member with OR

    Hi
    I am just having a mental block on how to create  a calculated member based on 2 different dimensions but can't get this to work.
    Using Adventure works 2012
    IIF(([Geography].[Country]].currentmember IS [Geography].[Country].&[Australia])
    OR ( [Employee].[Gender].currentmember IS [Employee].[Gender].&[M]) ,[Measures].CurrentMember,0)
    I'm just trying to create a dimension if it is Australia or the gender is male
    Regards

    Tab's concept is basically sound, there were just some round brackets and curly braces around the wrong way :)
    The following query works on my machine:
    WITH MEMBER [Geography].[Country].[AustraliaOrMale] AS 
    aggregate({([Geography].[Country].&[Australia],[Employee].[Gender].[All])}
    +
    {([Geography].[Country].[All],[Employee].[Gender].&[M])})
    SELECT NON EMPTY {[Employee].[Gender].members} ON COLUMNS,
    NON EMPTY ([Geography].[Country].ALLMEMBERS ) ON ROWS
    FROM [Adventure Works]
    WHERE [Measures].[Reseller Freight Cost]
    http://darren.gosbell.com - please mark correct answers
    Thanks Darren but it is not bringing back the correct total for reseller freight cost should be 1141666
    I have tried this which give the correct value but I'm not sure if the correct way
    With Member [Geography].[Country].[AustraliaOrMale1] as SUM(Existing({([Geography].[Country].&[Australia],[Employee].[Gender].[All Employees]),([Geography].[Country].[All Geographies],[Employee].[Gender].&[M])},[Measures].currentmember)) - SUM({([Geography].[Country].&[Australia],[Employee].[Gender].&[M])},[Measures].currentmember)
    Any input would be great

  • Join fact table with higher dimension level

    how do i join fact tables with higher dimension levels with discoverer?
    fact with detail at level C
    measure X
    dimension with
    D->C->B->A
    E->C
    level
    A B C
    1------1------1
    2------2------1
    3------2------1
    join between fact X and dimension level C
    X=3*C because of sum(X) in discoverer and 3xC in dimension
    is there a way to get correct values for X without creating a dimension like
    D->C
    E->

    another way of asking this is whether you can create a summary table in Discoverer at a higher level than a dimension's fundamental grain. In other words - the summary examples in the documentation all describe leaving out one or more of your dimensions... they are either left in or completely taken out. But, some of the most effective summarization occurs when you summarize daily data to a monthly level. Assuming that I have a sales table (at a daily level, and a key value sales_date), and a table date_dim (primary key sales_date), I would like to create a summary sales_month_summary where the sales are grouped on month_year (which is a field in the sales_date table).
    How is this done? I suspect that we can't use the date_dim table with the summary (due to the problems noted by the poster above). Do we have to create another table "month_dim"? Do we have to fold all of the desired date attributes (month, quarter, year) into the summary? Obviously we'd like to re-use all of the pertinent already existing date items (quarter, month, year, etc.), not recreate them over again, which would result in essentially two sets of items in the EUL. [One used for this month summary, and another used for the detail.]
    I searched the forum - someone asked this same question back in 2000 - there was no answer provided.
    The only other thought I have is to "snowflake" the date_dim into two tables and two folders, one at a date level, another at the month level. Then the detail tables can connect to date_dim (which is linked to month_dim), while the summary data can connect directly to month_dim.

  • How to create a table with events in smartforms?

    How to create a table with events view in smartforms?
    It doesn't like general table with header, main area and footer.
    for example:
    in smartforms: LE_SHP_DELNOTE
    table name is TABLEITEM(Delivery items table)

    Vel wrote:
    I am creating XML file using DBMS_XMLGEN package. This XML file will contain data from two different database tables. So I am creating temporary table in the PL/SQL procedure to have the data from these different tables in a single temporary table.
    Please find the below Dynamic SQL statements that i'm using for create the temp table and inserting the data into it.
    Before insert the V_NAME filed, i will be appending a VARCHAR field to the original data.
    EXECUTE IMMEDIATE 'CREATE TABLE TEMP_TABLE (UNIQUE_KEY NUMBER , FILE_NAME VARCHAR2(1000), LAST_DATE DATE)';
    EXECUTE IMMEDIATE 'INSERT INTO TEMP_TABLE values (SEQUENCE.nextval,:1,:2)' USING V_NAME,vLastDate;What exactly i need is to eliminate the INSERT portion of it,Since i have to insert more 90,000 rows into it. Is there way to have the temp table created with data in it along with the sequence value as well.
    I'm using Oracle 10.2.0.4 version.
    Edited by: 903948 on Dec 22, 2011 10:58 PMWhat you need to do to eliminate the INSERT statement is to -- as already suggested by others - eliminate the temporary table. You don't need it. It is just necessary overhead. Please explain why you (apparently) believe that the suggestion of a view will not meet your requirements.

  • Creation of Article with purchasing view.

    Hi,
    I am using BAPI_MATERIAL_MAINTAINDATA_RT  to create Article. I am able to create article using Basic view, Log. DC view etc.
    There is no purchasing view in HEADDATA. Also  fields like Purchase organization, net price etc are not present in any structure.How to create an Article  with purchasing view using this BAPI.
    Please help me in this regard.
    Regards,
    Kiran.

    Hi,
    I am using BAPI_MATERIAL_MAINTAINDATA_RT  to create Article. I am able to create article using Basic view, Log. DC view etc.
    There is no purchasing view in HEADDATA. Also  fields like Purchase organization, net price etc are not present in any structure.How to create an Article  with purchasing view using this BAPI.
    Please help me in this regard.
    Regards,
    Kiran.

  • BAPI_MATERIAL_MAINTAINDATA_RT ---Article with purchasing view

    Hi,
    I am using BAPI_MATERIAL_MAINTAINDATA_RT  to create Article. I am able to create article using Basic view, Log. DC view etc.
    There is no purchasing view in HEADDATA. Also  fields like Purchase organization, net price etc are not present in any structure.How to create an Article  with purchasing view using this BAPI.
    Please help me in this regard.
    Regards,
    Kiran.

    Hi,
    I had the same problem with this bapi. To activate the purchasing view
    I used WRF_MATERIAL_MAINTAINDATA_RT to create the materials.
    You must put attention how works the mm41 and fill the segments in this
    that you need.
    *& Report  ZTEST_BAPI_EXTENDEDUPDATE
    REPORT  ztest_bapi_extendedupdate.
    DATA: headdata TYPE bapie1mathead.
    DATA: return TYPE STANDARD TABLE OF bapireturn1.
    DATA: lwareturn TYPE bapireturn1.
    DATA: organizational_level TYPE wrfscreenvalues.
    DATA: clientdata  TYPE STANDARD TABLE OF bapie1marart WITH HEADER LINE.
    DATA: clientdatax TYPE STANDARD TABLE OF bapie1marartx WITH HEADER LINE.
    DATA: addnlclientdata TYPE STANDARD TABLE OF bapie1maw1rt  WITH HEADER LINE.
    DATA: addnlclientdatax  TYPE STANDARD TABLE OF bapie1maw1rtx WITH HEADER LINE.
    DATA: unitsofmeasure  TYPE STANDARD TABLE OF bapie1marmrt  WITH HEADER LINE.
    DATA: unitsofmeasurex TYPE STANDARD TABLE OF bapie1marmrtx WITH HEADER LINE.
    DATA: salesdata  TYPE STANDARD TABLE OF bapie1mvkert WITH HEADER LINE.
    DATA: salesdatax  TYPE STANDARD TABLE OF bapie1mvkertx WITH HEADER LINE.
    DATA: inforecordgeneral  TYPE STANDARD TABLE OF bapieina WITH HEADER LINE.
    DATA: inforecordpurchorg  TYPE STANDARD TABLE OF wrfbapieine WITH HEADER LINE.
    headdata-material = '000000000000400121'.
    headdata-matl_type = 'ZMES'.
    headdata-matl_group = '101210501'.
    headdata-matl_cat = '00'.
    headdata-ref_matl = '000000000000448590'.
    headdata-basic_view = 'X'.
    headdata-list_view  = 'X'.
    headdata-sales_view = 'X'.
    headdata-logdc_view = 'X'.
    headdata-pos_view = 'X'.
    organizational_level-material = headdata-material.
    organizational_level-matl_type = headdata-matl_type.
    organizational_level-matl_group = headdata-matl_group.
    organizational_level-matl_cat = headdata-matl_cat.
    organizational_level-ref_matl = headdata-ref_matl.
    organizational_level-purch_org = 'SPC1'.
    organizational_level-vendor = '20400353'.
    organizational_level-info_type = '0'.
    *organizational_level-plant = ''.
    *  Llena clientdata
    clientdata-material  = headdata-material.
    clientdata-base_uom  = 'ST'.
    APPEND clientdata.
    clientdatax-material  = headdata-material.
    clientdatax-base_uom  = 'X'.
    APPEND clientdatax.
    addnlclientdata-material    = headdata-material.
    addnlclientdata-sales_unit  = ''.
    addnlclientdata-li_proc_st  = 'B1'.
    addnlclientdata-li_proc_dc  = 'B1'.
    addnlclientdata-list_st_fr  = sy-datum.
    addnlclientdata-list_st_to  = '99991231'.
    addnlclientdata-list_dc_fr  = sy-datum.
    addnlclientdata-list_dc_to  = '99991231'.
    addnlclientdata-sell_st_fr  = sy-datum.
    addnlclientdata-sell_st_to  = '99991231'.
    addnlclientdata-sell_dc_fr  = sy-datum.
    addnlclientdata-sell_dc_to  = '99991231'.
    APPEND addnlclientdata.
    addnlclientdatax-material    = headdata-material.
    addnlclientdatax-sales_unit  = 'X'.
    addnlclientdatax-li_proc_st  = 'X'.
    addnlclientdatax-li_proc_dc  = 'X'.
    addnlclientdatax-list_st_fr  = 'X'.
    addnlclientdatax-list_st_to  = 'X'.
    addnlclientdatax-list_dc_fr  = 'X'.
    addnlclientdatax-list_dc_to  = 'X'.
    addnlclientdatax-sell_st_fr  = 'X'.
    addnlclientdatax-sell_st_to  = 'X'.
    addnlclientdatax-sell_dc_fr  = 'X'.
    addnlclientdatax-sell_dc_to  = 'X'.
    APPEND addnlclientdatax.
    unitsofmeasure-material   = headdata-material.
    unitsofmeasure-alt_unit   = 'ST'.
    unitsofmeasure-ean_upc    = '7702111342224'.
    APPEND unitsofmeasure.
    unitsofmeasurex-material   = headdata-material.
    unitsofmeasurex-alt_unit   = 'X'.
    unitsofmeasurex-ean_upc    = 'X'.
    APPEND unitsofmeasurex.
    "inforecordgeneral-info_rec ='5300002556'.
    inforecordgeneral-material = headdata-material.
    inforecordgeneral-mat_grp = headdata-matl_group.
    inforecordgeneral-vendor = organizational_level-vendor.
    inforecordgeneral-po_unit = 'ST'.
    *inforecordgeneral-base_uom = clientdata-base_uom.
    APPEND inforecordgeneral.
    inforecordpurchorg-material = headdata-material.
    inforecordpurchorg-vendor = organizational_level-vendor.
    "inforecordpurchorg-info_rec = '5300002556'.
    inforecordpurchorg-purch_org = organizational_level-purch_org.
    inforecordpurchorg-info_type = '0'.
    inforecordpurchorg-pur_group = 'GC1'.
    inforecordpurchorg-currency = 'MXN'.
    APPEND inforecordpurchorg.
    BREAK-POINT.
    CALL FUNCTION 'WRF_MATERIAL_MAINTAINDATA_RT'
      EXPORTING
        headdata             = headdata
        organizational_level = organizational_level
        badi_callmode        = '99'
      TABLES
        return               = return[]
        clientdata           = clientdata[]
        clientdatax          = clientdatax[]
        addnlclientdata      = addnlclientdata[]
        addnlclientdatax     = addnlclientdatax[]
        unitsofmeasure       = unitsofmeasure[]
        unitsofmeasurex      = unitsofmeasurex[]
    *    plantdata             = plantdata[]
    *    plantdatax            = plantdatax[]
    *    salesdata             = salesdata[]
    *    salesdatax            = salesdatax[]
        inforecord_general    = inforecordgeneral
        inforecord_purchorg   = inforecordpurchorg
    BREAK-POINT.
    READ TABLE return INTO lwareturn WITH KEY type = 'E'.
    IF sy-subrc NE 0.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
        EXPORTING
          wait = 'X'.
    ENDIF.

  • Issue with Sales Views in MM01

    Hi gurus,
    We need to create a material with only views for Basic Data 1&2, and Sales Org. Data 1, Sales Org. Data 2 and Sales General Plant data.
    The sales organization is created but when trying to assign the material (with existing Basic Data 1&2) to the Sales Organization the system is giving error "sales org. and distrib. channel invalid sales area".
    Any idea what additional settings are necessary to assign the material to the sales org. ?
    Thanks!
    VL

    Sales organisation itself is not enough, you have to define distribution channel also:
    SPRO > Enterprise Structure > Definition > Sales and Distribution > Define, copy, delete, check distribution channel
    Distribution channel has to be assigned to sales organisation:
    SPRO > Enterprise Structure > Assignment > Sales and Distribution > Assign distribution channel to sales organization
    Division should also be defined and assigned:
    SPRO > Enterprise Structure > Assignment > Sales and Distribution > Assign division to sales organization
    It's starnge that you want to create material master and still your config has such serious deficiencies...

  • Creating dimension in OMB script with only 1 level and no hierarchy

    Hi all,
    I have created some dimensions in the OWB client, that map straight 1-on-1 to a table. Those dimensions have only 1 level 'TOTAL' and no hierarchies.
    I am trying to create those dimensions using an OMB script, but it seems that when I bind the dimension level to a table, it =expects= me also to bind hierarchy levels to the table! However I have (dont want/need) a hierarchy?!
    The error message is:
    OMB00001: Encountered DIMENSION_KEY at line: 1, column: 2309. Was expecting one of: <EOF>
    The OMB code I have is:
    IMPLEMENTED BY SYSTEM STAR \
    DIMENSION_KEY BOUND TO COLUMN 'DIM_CAUSE_KEY' \
    LEVEL 'TOTAL' BOUND TO TABLE 'DIM_CAUSE' \
    LEVEL_ATTRIBUTE 'DIM_CAUSE_KEY' OF LEVEL 'TOTAL' BOUND TO COLUMN 'DIM_CAUSE_KEY' \
    LEVEL_ATTRIBUTE ...
    LEVEL_ATTRIBUTE ...
    After the LEVEL_ATTRIBUTEs the statement ends, so I say nothing about any hierarchies.
    If anybody could give me a hint, that would be much appreciated!!
    Ed

    It is finally solved...
    The keyword "SYSTEM" in "IMPLEMENTED BY SYSTEM STAR" shoudn't be there...
    Unfortunately I was overlooking that in the oh-so-clear syntax diagram in the OWB API and Scripting Reference..... )-;
    Let's move on.
    Cheers,
    Ed

  • Best Practice loading Dimension Table with Surrogate Keys for Levels

    Hi Experts,
    how would you load an Oracle dimension table with a hierarchy of at least 5 levels with surrogate keys in each level and a unique dimension key for the dimension table.
    With OWB it is an integrated feature to use surrogate keys in every level of a hierarchy. You don't have to care about
    the parent child relation. The load process of the mapping generates the right keys and cares about the relation between the parent and child inside the dimension key.
    I tried to use one interface per Level and created a surrogate key with a native Oracle sequence.
    After that I put all the interfaces in to one big Interface with a union data set per level and added look ups for the right parent child relation.
    I think it is a bit too complicated making the interface like that.
    I will be more than happy for any suggestions? Thank you in advance!
    negib
    Edited by: nmarhoul on Jun 14, 2012 2:26 AM

    Hi,
    I do like the level keys feature of OWB - It makes aggregate tables very easy to implement if your sticking with a star schema.
    Sadly there is nothing off the shelf with the built in knowledge modules with ODI , It doesnt support creating dimension objects in the database by default but there is nothing stopping you coding up your own knowledge module (use flex fields maybe on the datastore to tag column attributes as needed)
    Your approach is what I would have done, possibly use a view (if you dont mind having it external to ODI) to make the interface simpler.

  • I need create a column with level key...

    I need create a column with level key for city column in the location dimension, the same thing for village, ect.

    Hi Dapego,
    According to your description, you want to add an extra column with level key for city, and then add this column to location dimension as an attribute, right?
    In this case, you can define named calculation on the datasource view. Named calculations are Virtual columns that can be added on tables in Data Source View(DSV). This named calculation acts as a Column in your table and this column won't be reflected in
    your database.
    http://www.codeproject.com/Tips/660919/Introduction-to-Named-Calculations-in-SQL-Server-A
    http://msdn.microsoft.com/en-us/library/ms174859.aspx
    If I have anything misunderstanding, please point it out.
    Regards,
    Charlie Liao
    TechNet Community Support

  • 3 Levels Master Detail View Object with Java class interface

    Hi Developers,
    I've created 3 tables with one to many relations as below
    BOARD ------<- APPLICANT ------<- QUALIFICATION
    a board includes many applicants and an applicant includes many qualifications.
    When I add these tables to a Fusion Project, JDeveloper 11g helps me to add the Entity Links and View Associations automatically.
    Then, I defined these relations in an ApplicantModule's Data Model as below.
    [+] BoardVO1
          |
          |--[+] ApplicantVO1
                   |
                   |--[+] QualificationVO1The problem is: I cannot write any function in QualificationVO and publish it by client interface.
    I created a simple function with a single line (System.out.println(...) ) in QualificationVOImpl.java. and selected it in Client Interface. But when I execute it from the ApplicantionModel for testing, an oracle.jbo.NoObjException JBO-25003 is raised. with message: Object ... ApplicantVO1 of type ApplicationModule not found.
    Has anyone tried to implement some coding in the third level of a master details view structure as my example? How do you make it works?
    I'm using JDeveloper 11.1.1.3 with ADF BC.
    Regards,
    Samson Fu

    Samson,
    Looks like a bug (probably with the application module tester). I created your tables:
    create table board(board_id number primary key not null);
    create table applicant(applicant_id number primary key not null, board_id number not null);
    create table qualification(qualification_id number primary key not null, aplicant_id number not null);
    alter table applicant add a_fk foreign key(board_id) references board;
    alter table qualification add q_fk foreign key(aplicant_id) references applicant;I created a JDev project and got the same results. I've e-mailed a test case off to Frank.
    Frank - the method is indeed exposed on the VO instance, and I tried testing that way, but the AM tester gives the error as if it is looking for an AM instance with the VO's name.
    John

  • Can CWM2 API creating dimensions and cube reference a view

    Can CWM2 API creating dimensions and cube reference a view instead of a table.
    Can the following API reference a view instead of table
    For creating dimensions
    CWM2_OLAP_TABLE_MAP.MAP_DIMTBL_HIERLEVEL
    CWM2_OLAP_TABLE_MAP.MAP_DIMTBL_HIERLEVELATTR
    For creating cubes
    CWM2_OLAP_TABLE_MAP.MAP_FACTTBL_LEVELKEY
    CWM2_OLAP_TABLE_MAP.MAP_FACTTBL_MEASURE

    Hi!
    Yes!
    And I am using views sometimes.
    I am reading at this moment also the following...
    maybe someone can explain me this sentence...
    MULTIPLE FACT TABLES:
    "The CWM2 APIs also support multiple fact tables per cube. In this case, the data
    associated with a given combinations of hierarchies can be stored in a separate fact
    table. All the fact tables associated with a cube must have the same column
    structure."
    I get a fetch error message..'cause of this.
    What does it mean by "the same column
    structure" ???
    ODDS

  • Creating a cube with more than one dimension

    I have been able to create a cube with one dimension using our own data. I am able to view data from this cube in Cube Viewer and in a presentation created with BI Beans in JDeveloper.
    However, I have been unsuccessful in doing this when creating a cube with two dimensions. What am I missing?
    I have been using OEM to create the dimensions and cubes, etc. in a 9.2.0.4 database.

    You can use Analytic Workspace Manager 10.1.0.4 to create analytic workspaces (MOLAP) in Oracle OLAP 10.1.0.4. The Model View in this GUI tool utilizes the OLAP AW Java API that was introduced in Oracle OLAP 10g. This Java API fully abstracts the logical dimensional model from physical design.
    OWB Paris, which is currently in beta, likewise uses the OLAP AW API to create AWs. In addition, it can create ROLAP cubes via the OLAP Catalog CWM2 APIs. This is a change in APIs as the previous version used CWM1/Lite like Enterprise Manager. Also, for ROLAP cubes OWB Paris will automatically include MR_REFRESH in its scripts and will call the appropriate DBMS_ODM package in order to create materialized views.
    As for tutorials for creating a star schema, check with the Oracle Warehouse Builder forum.
    OWB Forum:
    Warehouse Builder

  • Can I create a dimension based on a view?

    The OLAP9201A allowes creating cube based on view, so does it also alowes creating dimension based on view?
    I want to using view to deal with priviledge issues.

    Thank you.
    The document says that I can create view based dimensions using cwm2. But when I tried to execute cwm2 packages' procedures, I always got error.
    For example, when I ran the following scripts under the schema 'CFA', I got error message.
    --my scripts
    begin
         cwm2_olap_dimension.create_dimension('CFA', 'TESTCWM2_DIM', 'TESTCWM2', 'TESTCWM2s', 'cwm2', 'TESTCWM2',null);
    end;
    --error messages
    The following error has occurred:
    ORA-06502: PL/SQL: 数字或值错误 : 字符串缓冲区太小
    ORA-06512: 在"OLAPSYS.CWM2_OLAP_MANAGER", line 380
    ORA-06512: 在"OLAPSYS.CWM2_OLAP_MANAGER", line 397
    ORA-06512: 在"OLAPSYS.CWM2_OLAP_DIMENSION", line 139
    ORA-06512: 在line 2
    --my comments on error messages
    The Chinese text means:error of number or value: the string buffer is too small.
    What's wrong?

  • Creating a .pdf with different page views

    I'm tyring to create a .pdf with different page views.  For example as the viewer goes through the .pdf some pages I would like viewed as "single page view" and others "two page view".  Is this possible?   I'm working with Adobe Acrobate Pro.  Thanks for any suggestions.

    It's possible to use the Page Open actions to trigger a view mode change but it's messy - if the user tries to override them because they prefer to zoom in, etc. then they'll get very annoyed when things keep resetting.
    To create a Page Open action, open the thumbnails panel, right-click on a page, choose Page Properties, then the Actions tab. You can use the Execute a Menu Item tool to fire one of the view modes.

Maybe you are looking for

  • Greyed Out "Free Space" in Disk Utility

    Hi I have a problem with my main Logical Volume Group / Partition. So My main Logical Volume Group (Macintosh HD) was separated into 2 partitions. I decided to delete the second one, and once the process started in Disk Utility, it crashed. Now if I

  • CVS and JDeveloper 9.0.3

    Hi, I tried to activate source control CVS inside JDeveloper. In the tools menu I activated CVS, but I got always the message "The CVS client is not installed or not located in your system environment path". I'm working with a Windows XP machine. Win

  • ADF - Collections with Arrays Not Displaying

    I am using JDeveloper 10.12. Within the applicaiton I am developing I have the following: nominalRecord - Java Bean nominalRecordCollection - Collection of nominalRecords I have generated a data control from the nominalRecordCollection. The data with

  • Can't login with Wireless Keyboard

    Hello, My daughter's iMac wont accept input from her wireless keyboard: we're stuck trying to login. She has set up the login screen when it boots - to keep her sister out . It does recognise her wireless mouse which will move the pointer around the

  • Add search bar within an image

    I'm wondering how to embed a search bar in the middle of an image. I googled this but I couldn't find what I was looking for. If anyone can help me it would be greatly appreciated. Thank you