I have several hundred rcaster burst address book values needing to be managed. I was hoping that someone could point me in the right direction for a mgmt concept for high number of burst values that would still be accessable via the webfocus rcaster burst reporting method.

Can I use some kind of external DB to manage my distribution lists that would still be accessable by the report caster burst feature? (like ms/sql or ms/access ?) thx

Ken

You can try using the distribution file to burst out reports.

going a little further on that last thought, you can dynamically create a distribution file that RC can use - so whether you build it on the fly (as in a pre-processing step) or you store names/addresses/burst values in the DB of your choice, it can be done. Storing them in another DBMS lets you use whatever management tool you want. This, of course, assumes that you are licensed to read that DBMS as a WebFOCUS data source.

you can read the bot***.foc files directly, and write a modify routine, depends on what database you decided upon for your caster repository. To get started on reading your own bot***.foc files, read this
BTW, Caster can use mailing lists set up on your exchange server, which (one hopes) someone in personnel handles for you..

Re:
>>
BTW, Caster can use mailing lists set up on your exchange server, which (one hopes) someone in personnel handles for you..
>>

This sounds interesting. Can you clarify a couple things on that note. Would I be able to utilize an exchange server distribution list AND the rcaster burst dist method? That would be optimal I think if posible.. thx so much.
Ken

don't know. to burst, you need two values, the burst value in the report followed by the address.