Recent content by Subhashab

I mean where clause in the DP and not at report level

HI Moving the repository created in Oracle DB should be a straight forward exercise. Use the Oracle import/export utility to move the repository table/data to the new database. after the data has been moved run supervisor module. Click in the admin button and choose recover bomain option. In...

you could create objects in designer with the @promt clause. for example <start date> with defintion @prompt('!Enter Start Date','D',,,) and then reuse the object in your where clause where ever u want.

Since you have a field which indicates which row is the duplicate. (Y/N field). create alert with condition <indicator> = 'N'. apply this alert to all columns you want to highlight.

why don't you break on the mirrorwillcod and apply a count on willcod. this format will be more intutive to the user.

Delta refresh is also called as incremental refresh. In the method of refresh only the data created or modified after the last refresh is delivered to the DW loading program. Performance is the only benefit of the delta refresh. however it need support from the source to implement delta...

i think you can do this only using webI. In BO links do not work. however even in BI you have to write the correct url call to show the report.

where have you used the formula in designer or BO

check for the installation folder Program Files\Business Objects\BusinessObjects 5.0 all exe files are under this folder. you can manually create the link in start menu by creating link and copying to the correct folder under Documents and Settings.

are u having two DP and u are linking them. or what exactly you mean by linking.

your filter clause is generated using the having clause so make sure that the dimension selected is ok.

Have you mentioned max in the sql definition of the measure object. And where are u applying the filter in the DP or BO (BO u you cannot apply filter of summary varaibles created in BO.

Hi paul, I am not sure i understood ur problem . can you explain with some dummy data.

First please mention what is the logic based of which you decide which of the 3 fields should be used to join to table b. And is only one of the three b tables is used in any sql generated in that case you can eliminate the aliases else you have to stay with ur current design Assuming this is...

check you where clause you must have mentioned where clause more than the primary key fields that is why the update/insert fails.