Question on use in Analyst

[StuartS]

Version 8.4.0 FP 1

I have a D-Cube where users select two fields based on D-List formatting.  The D-List used for formatting is different for each field and so the IID's are different.

This D-Cube is used to create two ASCII files that are then imported into A Tables, @ATabImportDelimitedText.

The values in D-Cube will change and so the A Tables will change.

The A Tables are used in a Contributor Administration Link thaqt is called from a macro.

My issue is that if one of the A Tables is empty due to no user selection in the original D-Cube the Contributor macro fails.

I have two lines for investigation.

1, Combine the two A Tables into one.  I dont want to use a macro in an Excel workbook called from a manager screen.

2, Alter the Contributor Macro to handle the situation where the A Table in one link is empty.  Note, I do not want two contributor macros unless this is the only way.

Any ideas??

Regards

Stuart

[Rutulian]

Hi Stuart,

If the problem's only occurring when it's actually empty, could you maybe add a line that maps to a dummy item not included in the Contributor model so that there's always something in there?  Sounds ugly to me, but it's another option to consider.

I'm interested in how you'd alter the Contributor Macro to test the emptiness of the a-table, is that possible?  Sounds like the best way to do things if it is, if you end up needing 2 Contributor macros you could always nest one inside the other with the 'Execute Macro' macro step, so from an execution perspective you only have to kick one off.

Good luck!

R

[StuartS]

Hello

Thank you for your reply.  Something to ponder.

My original email provided an example of two A Tables.  I now have 3.    Dont ask.....

The problem is that any one can be empty. (The values in the A Tables are elist names - there is a need to transfer data across elists,)

Your suggestion of a dummy elist item to ensure the macro doesn't fail is interesting.  Yes, it is messy/ugly but would work.  My only reservation is it creates a monster for access tables with having to hide it in each cube.  Note the access tables for some cubes are created from admin routines based on user selection.

My current solution is three macros, each one synchronising and executing an admin link.  Ill see if the customer/users will accept this.

Thank you

Stuart