Error in Dimension Formula

Hi,
There are dimension formulas maintained in my Account dimension. When I am processign the dimension, the processing is failing telling that for few of the members, the formula is getting in to an infinite recursion. I have checked the code a lot of times. However, unable to understand why this error is coming.
The formula for one of the dimension members looks like this
((Account.H2.PL332000+Account.H2.PL331000)/(val([Time].properties("Monthnum"))/12))/
([Account.H1].[FTE_R_D],[ACCDETAIL].[FTE_TOT]),SOLVE_ORDER=50
Kindly help me.

Thanks Sorin for the response.
In that case, what can be the solution?
I have seen examples in which members from different tables, like accdetail, are used in the formulas. They are working absolutely fine.
My understanding says that the different hierarchies are stored in different tables. So, hierarchy 1 will be stored in the table Account.H1 and hierarchy 2 will be stored in Account.H2.
If, we are able to use members which is present in accdetail table, ideally we should be able to use the members which are present in Account.H2 as well. Its just the table from where we are fetching the members.
Kindly help me if I am wrong in my concept

Similar Messages

  • Error in Dimension formula to find the average price

    Hi all,
    I have tried a dimension formula to find the average price of Product.
    if the product is a parent level member then average price should be the average of the list price,other wise it should be the list price itself.
    IIF([PRODUCT].CURRENTMEMBER.PROPERTIES("CALC")="N",[KEYFIGURES].[LISTPRICE],AVG(DESCENDANTS([PRODUCT].CURRENTMEMBER,[KEYFIGURES].[LISTPRICE],LEAVES)))
    While i tried the same i received some strange error , i don know whether its having some dependency on the Customer dimension. since K0030101 is a memebr belonging to CUSTOMER dimension.
    MDX statement error:"Value K0030101 for characteristic /CPMB/U6D7SXT un"
    I'm not sure whether its an error with  the formula i created or any dependancy issue or whether this scenario is possible  using  dimension formulas or not.
    Thanks in advance .
    Anila Mohan

    Hi everyone!
    We are using BPC 7.5 NW SP08 and we've had the same error message while adding a formula to the Account dimension:
    'MDX statement error: "Value 1 for characteristic /CPMB/S9D7Q23 un".
    We then checked in BW for /CPMB/S9D7Q23 and found out that it was the Product dimension.
    The solution for the issue was quite interesting. I had seen in another post that sometimes CALC property was not correctly determined for SP08. The solution proposed was to edit dimension members, clear ParentH1 column, process dimension, re-edit, paste back ParentH1 values and process dimension again. This corrected CALC property problem.
    It also worked for my case. After doing it to Product dimension I tried again to set the formula in Account dimension and it worked!!
    Hope this helps.
    Regards,
    Luigi Laporte

  • BPC 7.5NW SP08: "unknown MDX error" message for simple dimension formula

    Hi everyone!!
    We are facing many different issues concerning dimension formulas and
    script logic. Maybe it's something related to SP08. For instance,
    consider the following:
    - there is a dimension named P_Account, with members Price, SalesCost,
    and others
    - there is a dimension named P_Product, which consists of a hierarchy,
    for instance: Prod1 with two children, Prod1A and Prod1B
    We want to set the following dimension formula in P_Product for Prod1 member:
    IIF([P_Account].CURRENTMEMBER.PROPERTIES("ID") = "Price", Null, 1)
    that is, we wanted to try to be able to avoid summing Price, returning
    Null for (Price, Prod1). Later we would try to replace "1" with the
    appropriate formula to sum children of Prod1 for all other members of
    P_Account. The result is an odd error: "MDX statement error: unknown MDX
    error" (or something similar, since I get the error message in portuguese).
    We have spent almost two days studying alternatives in SDN Forum, blogs,
    google, etc, trying to find a reason for the error but couldn't find it.
    Could anyone help on this one?
    Thanks!
    Luigi

    Hi everyone!
    After contacting SAP, we were asked to try to reproduce the error in APSHELL. I did the following:
    1) created another application set, copying APSHELL, named it TESTAPPSET;
    2) added two members to dimension P_ACCT (ID, ACCTYPE, SCALING, RATETYPE):
       (PRICE, INC, Y, END)
       (SALESCOST, INC, Y, END)
    3) saved to server and processed P_ACCT dimension successfuly
    4) added a UD dimension copied from P_Activity, named P_Product
    5) deleted all members of P_Product, processed the dimension sucessfuly
    6) added FORMULA property to P_Product, with size 200
    7) added three members to P_Product (ID, PARENTH1)
       (Prod1, "")
       (Prod1A, Prod1)
       (Prod1B, Prod1)
    8) saved to server and processed the dimension successfuly
    9) edited P_Product members and added the following as FORMULA for Prod1:
    IIF([P_ACCT].CURRENTMEMBER.PROPERTIES("ID") = "PRICE", Null, 1)
    Result was sucess!!
    10) edit P_Product again and removed the formula, saved to server and processed dimension successfuly;
    11) created an Application named SALES, type Financial Report, copied from PLANNING with dimensions
    12) edit dimensions, removed P_Activity and added P_Product to the list
    13) went back to step (9) and tried to add the formula again, saved to server and processed P_Product dimension. Result was success again!!
    So I imagined the issue might be caused by the user I was log in with. I went back to our application set, logged in as BPC_SYSADMIN and tried to set the formula again and it didn't work. User was not the problem.
    Since I had tried all the above creating everything with all UPPERCASE, I decided to try the following Formula
    IIF([P_ACCOUNT].CURRENTMEMBER.PROPERTIES("ID") = "Price", Null, 1)
    that is, P_ACCOUNT instead of P_Account. Result: success in processing dimension!!! And the formula worked as expected when I opened an Input Schedule to test it.
    When I check my dimension list in BPC Admin it says P_Account (mixed case), instead of P_ACCOUNT (all uppercase) since it was the way we created it.
    So, I spent 1hour to do the whole test, but it worked. I sent two questions/requests for correction or improvement to SAP:
    I) which case should be used in formulas? given I see P_Account in Dimension list, how should I know that I should write formulas with P_ACCOUNT, all uppercase?
    II) could BPC provide more descriptive error messages when processing dimensions and validating script logic? a simple error message such as "unidentified command or reference at P_Account" or anything similar would have saved us 4,5 days of work! it's a lot!
    Thank you guys for your support!!

  • Dimension formula error

    Hello all,
    I have created the following dimension formula in dimension Groups(Currency):
    'IIF([DataSrcDim].H1.CurrentMember is [DataSrcDim].H1.[20_ELIM], [GROUPS].MemberX-[GROUPS].MemberY-[GROUPS].MemberZ-[GROUPS].MemberW,NULL),SOLVE_ORDER=50
    In short the objective of this formula is to perform a calculation (X-Y-Z-W) on GROUPS dimension members if the DATASRC dimension member is 20_ELIM.
    However, I get the following error when I process the GROUPS dimension:
    -"[GROUPS].[#ABCD] The dimension '[DATASRCDIM]' was not found in the cube when the string, [DATASRCDIM].[H1], was parsed"
    I get this error even though the DATASRC dimension exists in th cube/application.
    Would any of you have an idea why this error occurs and if so how can I correct it?
    Thank you & regards
    Raja

    Hi,
    Please try the formula as:
    IIF([DATASRC].CurrentMember = "20_ELIM", [GROUPS].[MemberX]-[GROUPS].[MemberY]-[GROUPS].[MemberZ]-[GROUPS].[MemberW],NULL);SOLVE_ORDER=50
    Hope this helps.

  • Problem Iif formula. MDX dimension formula

    Hi experts,
    I have a quite problem with tolerance in validation rules. When user tries to change Workstatus, system don't let it, because it detect that validation account is not equal to zero, however value of this account seems to be zero.
    I know tolerance doesn't works fine on 7.0 MS version. Because of this we are trying to create an MDX formula on dimension account, but system give us this error.
      - [CUENTA].[H2].[#X000] Parser: The end of the input was reached.
    Our Dimension AccountL (Cuenta) has 3 hierachies. BLOQ_FASEC member is a parent member which sum all validation account.
    We are trying to introduce a formula in other account member, giving to this one a tolerance.
    Formula introduced is this one:
    Iif(Cuenta.H2.BLOQ_FASEC < 0.5 and Cuenta.H2.BLOQ_FASEC > -0.5,0,Cuenta.H2.BLOQ_FASEC)
    Could you help us?

    Hi again,
    Just to be on the same page...
    - You have 3 hierachies in your Excel dimension file  (PARENTH1, PARENTH2, PARENTH3)
    - You have 3 Formulas columns in your Excel dimension (FORMULAH1, FORMULAH2, FORMULAH3)
    - What I would like to know is, what are the dimension properties assigned to your dimension (Admin console --> Maintain dimension properties...). Here, you should ONLYhave one FORMULA dimension property assigned, even using multiple formula columns in you Excel file.
    Then, if you setup that in that way, this is correct... But you should write your dimension formula only in FORMULAH2 column.
    In fact, you cannot mix members from hierarchy 1 to calculate a member for hierarchy 2 for example. So, in one hierarchy you can just use members from that hierachy. Can you confirm that?
    Then, could you also confirm that all your dimension formulas are using the correct syntax (WITH BRACKETS)..
    Example: "&#91;Cuenta&#93;.&#91;H2&#93;.&#91;BLOQ_FASEC&#93;"...
    Best Regards,
    Patrick

  • MDX Dimension formula - sum using property

    Hi All,
    I am trying to add a dimension formula on the account dimension sheet and the goal is to add all the accounts that have a property TEST='Y' into a new account TESTACCOUNT
    Here is the formula that I am using but it errors out while processing.
    ID----
    FORMULA
    TESTACCOUNT----
    SUM([ACCOUNT].[H1].properties("TEST")="Y"),solve_order=10
    Can you please tell me where I am going wrong.
    Thanks in advance for your help.
    Swaroop
    Edited by: SwaroopLalam on Aug 13, 2009 4:18 PM
    Edited by: SwaroopLalam on Aug 13, 2009 4:19 PM

    Hi Petar,
    Thanks for your prompt reply. I tried the following and even that did not work. Am I doing something wrong here? Please see the error I received while processing the dimension;
    'sum(FILTER(descendants(ACCOUNT.[TESTACCOUNT],99,leaves),account.properties("TEST")="Y"),measures.periodic),solve_order=15
    ERROR:
      - [ACCOUNT].[H1].[#TESTACCOUNT] CustomRollupFormula([Account].[Account_H1_ID6].[TESTACCOUNT]) (1, 61) The 'Account' dimension contains more than one hierarchy, therefore the hierarchy must be explicitly specified.
    after that I gave the Heirarchy [H1], below;
    'sum(FILTER(descendants([ACCOUNT].[H1].[TESTACCOUNT],99,leaves),account.properties("TEST")="Y"),measures.periodic),solve_order=15
    ERROR:
      - [ACCOUNT].[H1].[#TESTACCOUNT] CustomRollupFormula([Account].[Account_H1_ID6].[TESTACCOUNT]) (1, 65) The 'Account' dimension contains more than one hierarchy, therefore the hierarchy must be explicitly specified.
    Thanks,
    Swaroop
    Edited by: SwaroopLalam on Aug 17, 2009 5:14 PM

  • Dimension Formulas in NW

    Hello All,
    I am trying to implement account dimension formulas for the calculation of ratios, but while it is processing successfully, I am not seeing any results.
    A couple of questions:
    1. Do dimension hierarchies have to be qualified in NW as it does is MS?
    2. Does the function Val not work in NW? I am trying to use the value in the weeksinperiod property of the time dimension in the formula. In the MS version, I used to have to convert the property value to a numeric value in the formula. When I use it in NW, I am getting as error for the function, Val.
    Below is my formula. If anyone could offer some guidance, I would really appreciate it.
    IIF([AccountCC].[EARNED_HOURS_2]=0,NULL,[AccountCC].[EARNED_HOURS_2]/[TIME].CURRENTMEMBER.PROPERTIES("WEEKSINPERIOD"));SOLVE_ORDER=4
    Regard,
    karen

    I just noticed the message removed the brackets around my dimension names. I forgot to set the formula as code. Here it is again.
    'IIF([AccountCC].[EARNED_HOURS_2]=0,Null,[AccountCC].[EARNED_HOURS_2]/[TIME].CURRENTMEMBER.PROPERTIES("WEEKSINPERIOD"));SOLVE_ORDER=4
    Regards,
    karen

  • Error : Period dimension 'Period' is missing a Base Time Period member 'Jun' that has been deleted since the last deployment. Base Time Period members cannot be deleted once the dimension is deployed

    HI,
    I am using V11.1.2.2 Hyperion Planning. I am currently getting an error:
    Error : Period dimension 'Period' is missing a Base Time Period member 'Jun' that has been deleted since the last deployment. Base Time Period members cannot be deleted once the dimension is deployed
    This is what i got when i tried to add alternate hierarchy to my shared dimension. I tried to delete it and it messed up.
    NOw it wont deploy my application.
    Can any one suggest.
    Thanks in advance
    Cheers,
    XXX

    EPMA!!!!! EPMA!!!!
    I'm playing around with it to write a blog post and it is crazy. Only possible workaround (till now i'm not able to figure out a solution to it) is to copy the application and deploy it as a new one. Take copy of all objects (forms, tasklist etc). Delete the corrupted application and rename the new one to old.
    Regards
    Celvin
    http://www.orahyplabs.com

  • OBIEE Evaluate - "Essbase error : Repeated dimension in MDX query"

    Hi,
    I'm using OBIEE 11.1.1.6.2 BP1 on top of Essbase.
    I have a project dimension in Essbase with three levels - Total Project -> Project Class -> Project. I have created a new logical column in OBIEE to query two levels from project dimension, using evaluate function as below:
    Evaluate('%1.Members, %2.Members',  "Oracle Hyperion Planning"."ASOCUBE".""."Planning"."Gen2,Project" ,   "Oracle Hyperion Planning"."ASOCUBE".""."Planning"."Gen4,Project" ).
    The above column when used in analysis, works fine, returning "Total Project" and all the projects. It breaks however when any filter is applied on project dimension with the following error:
    "[nQSError: 96002] Essbase Error: Repeated dimension [Project] in MDX query".
    I donot have any MDX skills and would appreciate if anyone can explain this error and provide any workaround for this. Here's the MDX that fails:
    With
      set [_Project0] as '{[Project].Generations(2).Members, [Project].Generations(4).Members }'
    select
      {} on columns,
      {{[_Project0]}} properties GEN_NUMBER on rows
    from [ASOCUBE.Planning]
    where ([Project].[1000000-Treatment Plant])
    Many Thanks

    This issue regarding BIEE
       because MDX is wrong
    With
      set [_Project0] as '{[Project].Generations(2).Members, [Project].Generations(4).Members }'
    select
      {} on columns,
      {{[_Project0]}} properties GEN_NUMBER on rows
    from [ASOCUBE.Planning]
    where ([Project].[1000000-Treatment Plant])

  • Using Dimension Formulas to sum data based on different criteria

    Hi all,
    I am trying to use a u201CDimension Formulau201D to perform the following calculation:
    We have an account dimension which has 2 important properties:
    1.     CRITERIUMTYPE: This property can have 3 different values: u201CWERKu201D, u201CINVu201D OR u201CLIQu201D
    2.     ACCTYPE: This property can have 2 different values: u201CEXPu201D or u201CINCu201D
    The client wants to have a report that sums data based on these 2 properties. An example will help to clarify this:
    ACCOUNTS     CRITERIUMTYPE     ACCTYPE     VALUE
    ACCOUNT A         WERK                          EXP               100 u20AC
    ACCOUNT B         WERK                          INC               150 u20AC
    ACCOUNT C         WERK                          EXP               200 u20AC
    ACCOUNT D         WERK                          INC               300 u20AC
    ACCOUNT E         INV                          EXP               50 u20AC
    ACCOUNT F         INV                          INC               100 u20AC
    ACCOUNT G         INV                          EXP               200 u20AC
    ACCOUNT H         INV                          INC               500 u20AC
    The clients wishes to see this data in the following way:
    CRITERIUMTYPE     ACCTYPE     VALUE
       WERK                         EXP              300 u20AC
                                        INC              450 u20AC
       INV                         EXP              250 u20AC
                                     INC              600 u20AC
    In order to achieve this I have created several new accounts, one for each combination e.g.: Account WERKEXP is used to sum the data on the combination CRITERIUMTYPE=WERK and ACCTYPE=EXP. I have created a dimension formula in my account dimension but this is where I am stuck. I have created the following formula to calculate the account WERKEXP:
    IIF([BUDGETPOSITIE].CURRENTMEMBER.PROPERTIES("ACCTYPE")="EXP",IIF([BUDGETPOSITIE].CURRENTMEMBER.PROPERTIES("CRITERIUMTYPE")="WERK",[BUDGETPOSITIE].CURRENTMEMBER,0),0)
    The problem with this formula is the following:
    The formula will add all amounts that meet the 2 criteria mentioned in the formula, EXP and WERK, but as soon as it finds an accounts that does not match the 2 criteria it will set the account WERKEXP back to 0. I need to know if there is a way, using dimension formulas, of adding these values together without the new account being set to 0 as soon as one of the accounts it needs to check does not meet 1 of the 2 criteria.
    We are working on SAP BPC 7.5 for NW with SP04
    All help is very much appreciated!
    Kind regards,
    Stefano

    Hi,
    You can also use ParentHn property to have different grouping of accounts within the dimension.
    So in your case rather using the member formula you can have four accounts and add them in the Parenthn property for grouping it.
    1. The Solution proposed by Nilanjan is specific for a Report/IS and Performance will be good
    2. My solution will be global something similar to MDX formula, but performance may be slightly lesser than using excel function.
    Hope this helps,
    Regards,
    G.Vijaya Kumar

  • 'Essbase Error: Repeated dimension [Accounts] in MDX query'

    Dear Essbase Gurus,
    I have an error in a query passed to my Essbase cube from an OBI front end, but the errors states quite clearly that it is an essbase error:
    'Essbase Error: Repeated dimension Accounts in MDX query'
    This is the query it generated:
    With
    set Accounts3 as 'Accounts.Generations(3).members'
    set Attribute Calculations2 as '[Attribute Calculations].Generations(2).members'
    set Events5 as 'Events.Generations(5).members'
    set Month3 as 'Month.Generations(3).members'
    set Scenario2 as 'Scenario.Generations(2).members'
    set Year2 as 'Year.Generations(2).members'
    set Axis1Set as 'crossjoin ({Accounts3},crossjoin ({Attribute Calculations2},crossjoin ({Events5},crossjoin ({Month3},crossjoin ({Scenario2},{Year2})))))'
    select
    {Measures.Total e-revenue} on columns,
    NON EMPTY {Axis1Set} properties ANCESTOR_NAMES, GEN_NUMBER on rows
    from Richmond.RichPOC
    As an Essbase newbie I'm unfamiliar with mdx and have no idea what this means, any help would be appreciated.
    Thanks
    Ed
    Edited by: Ed Higgins, AltiusConsulting.com on Oct 15, 2008 9:26 AM

    Hi garycris,
    Thanks for taking a look, I fear you may have hit the nail on the head, as I mention we are reporting on this using OBIEE, so we have imported the cube (BSO) into our OBI repository, OBI flattens the cube to make it look like a star schema it doesn't recognise the Accounts dimension correctly so we have to set it to be of type 'Other' after we have imported it, otherwise none of the figures in the Accounts dimension are actually reported (you can see the members but when included in a query no data is returned).
    Another issue we found was that OBIEE appeared to substitute the name 'Measures' for Accounts when building the query, so we made 'Measures' the default alias for the Accounts dimension, to add to the issue I probably should have mentioned that the aggregation rule in OBIEE for this fact column has been set to SUM rather than External_Agg, but Oracle support have previously indicated that this is OK to do. The issue originally arose because we wanted to extend on of our dimensions with additional attributes stored in a SQL database table.
    Sorry it is all a bit messy, the whole OBI with Essbase as a source is still relatively new, and it looks like there may be a few things for the mighty O to iron out, I posted this in here because the OBIEE forum has no posts with similar issues, so thanks for your help so far and anything else you can add.
    Ed

  • Universe Designer: Error getting dimensions for cube

    -Using Business Objects Edge 3.1 SP2
    -SAP BW 7.0 (patch level 21)
    This is quite odd behavior that seemed at first an authorization issue, but now I am uncertain.
    -Attempting to create a Universe based on a Infocube.
    -Universe connection is created with no problem using user 'ABC'
    -Using Universe Designer on the BOBJ server, no issues creating the Universe
    -Using Universe Designer on a users desktop, the Universe fails to create with error message:
    A runtime exception has occurred. (Error getting dimensions for cube $0SD_C03 (catalog $INFOCUBE): Unknown error)
    -Change the connection to use user 'DEF', the Universe creates just fine on the desktop
    -Behavior is not exclusive to one BW object, happens no matter what 'ABC' tries to access from this desktop
    So, at first I am thinking authorizations, but then the universe create would fail on the server as well.  If it is environmental, what could possibly affect this behavior.
    Any ideas before I submit to SAP Support?
    Edited by: Kevin Smolkowicz on May 5, 2010 12:40 PM
    Edited by: Kevin Smolkowicz on May 5, 2010 12:41 PM

    Oddly enough it was an authorization issue.
    When authenticating against the SAP source system from Universe Designer on either the workstation or server, both traces show a missing authorization for RFC_NAME = RASB
    This setting is not found in referenced SAPu2019s guides or whitepapers under suggested authorizations for Universe create.  What remains unexplained is why using the same credentials from 2 different computers had a different response.

  • Dimension Formula versus Script Logic that runs on default

    Hi Experts,
    Which is better to use dimension formula or script logic that runs on default? We have a lot of dimension formulas and when noticed that it has a huge impact in the performance of our AppSet. When we try to remove them, the performance seems better. We we're thinking of transforming these dimension formulas into script logic which will run by default instead. Right now I'm hesitant with two things, 1.) Will there be improvement in performance if I all these formulas are run at default via script logic? 2.) The maintenance seems to be much more complex for the user if we use script logic.
    Thanks,
    Marvin

    Hi Marvin,
    Actually you pointed very well the advantage and disantavage regarding dimension formula.
    Dimension formula are executed into run time which means that value are not calculated. Of course this will have an impact regarding performances.
    Usually our recommendation is to use dimension formula just when yoiu have KPI's to calculate which will be very difficult to be implemented into SQL scrip logic or when you have very simple calculation like Account A = Account B+ Account C.
    For other calculation we advice our customer to use script logic.
    But attention:
    Default formula should not become very heavy because you will arrive into other issue with performances.
    When you will send data if default formula script will be heavy you will arrive into situation to wait may be minutes just to send one figure and of course this will be not acceptable for users.
    So you have to use script logic but you have to run into batch mode (schedule package) that script logic.
    Into default formula you have to keep just minimum (you have to calculate just figures which have importance for user imediat, real time).
    Also you have to be aware that moving dimension formula into scrip logic actually your fact table will grow a lot because the number of records generated will be probably 3-4 times bigger than number of records from fact table with dimension formula.
    Maintenance of script logic is more complex than dimension formula and you pointed very well this.
    So it is a balance and I tried o provide you suggestions or best practice when you have to use dimesnion formula and you have to avoid dimension formula.
    I hope this will help you to arrive to best combination for your application.
    Kind Regards
    Sorin Radulescu

  • Error in a formula function (routine 66 ), record 4,161 RSAR 535

    Hi Experts,
    I am facing this issue while loading form DSO to Cube. So i am using
    Maximum Number of Errors per Pack  more then 1000 to skip the error records.
    In Error stack i get the below error :
    Error in a formula function (routine 66 ), record 4,161 RSAR 535
    Can any body help me on this.
    Thanks in advance
    Mohan.

    i am doing datamart load ie DSO to cube
    so while loading in DTP in update tab i have selected max no of error recods to be skipes = 9000 this will ignore the records if at all there are error records in the flow.
    i know there are few records. but what i want is to identify wht the error in the record is
    when i try to chk the records in Error stack if i selet  a record to change with change mode i also get a pop up with the error msg
    Re: Error in a formula function (routine 66 ), record 4,161 RSAR 535
    Which i dont really under stand what and were the error is
    i even compared the data of correct record which is alredy processed to the cube.
    I could not find much difference
    mohan.

  • Error in a formula function (routine ROUTINE_9998), record 0

    Hi Experts,
    i have an issue while loading from cube to ODS. The load fails with the following message:
    Data records for package 1 selected in PSA - 1 error(s)
    Record 0 :Error in a formula function (routine ROUTINE_9998 ), record 0
    Please help me... Thanks in Advance!

    Hi,
    Prob, it could be passing invalid date to DATE_WEEKDAY!() function.
    Regards,
    -Vj
    Edited by: Vijaya Bhaskar Bodanapu on Jan 16, 2009 3:24 PM
    Edited by: Vijaya Bhaskar Bodanapu on Jan 16, 2009 3:25 PM

Maybe you are looking for

  • Home sharing on but, can not share from laptop to desktop.

    I am trying to share songs from my iTunes account to my husbands. I am on my Macbook and he is on the desktop. We both followed the directions given through iTunes but we are still unable to import from each other. His library opens completely on my

  • Using Adapter with Cordless Phone

    Hi everyone!  My family and I are going to live in South America next week and need help deciding whether to buy the Skype Adapter or the Dual phones.  If we use the adapter and get an online number, if someone calls our online number, can we answer

  • Error message 499 when updating itunes

    When recently updating itunes to 10.1, I have gotten an error message each time saying the itunes store is unavailable and I should try back later (error 499). It appears as though the error is with my computer, but I am not sure what that could be!

  • Changing the Check Box color when selected/deselected

    How do I do this using the Action tab in Check Box Properties within Acrobat 7.0 (NOT DESIGNER)? I added the check boxes to the .PDF using the check box tool (Box Only-No Text). I am trying to fill the box green when selected and yellow when not sele

  • Can't phone a specific number on my 7373

    Can anyone help - my neice can't phone a specific number on her phone does anyone know what the problem could be. Have checked the number barring etc. Any tips ??