The easy way for messages is to redefine d_defined_messages in your app or
corp layer and change the table name to your standard. If you export the
object and carefully edit the source it is pretty quick. But you will still
have problems with the Security services (far too many objects to override).
What we did initially for the security service was to create the tables with
our naming standards and then create views to those tables with PFC-friendly
names.
However, in the end we decided to violate our table naming standard with a
so-called "PFC Exception" to the rule.
> -----Original Message-----
> From: Theisen, Timothy J. [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, February 02, 2000 10:19 AM
> To: 'PFCSig'
> Subject: PFCSIG PB/PFC 6.5 - Anyone modified the name of the error
> service "messages" database table to another table name?
>
> We have naming conventions for tables in our database, and the error
> message
> table
> that is used for storing error messages when using the PFC error message
> service
> is called "messages" ... there does not appear a simple way of doing
> this,
> but
> maybe I am missing something obvious.
>
> Is there a simple way to change this error message table name to another
> name
> (but obviously keep the same structure) so that the table name can conform
> to
> the standards?
>
> Thanks in advance.
>
> > [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS,
> ADDRESS
> > A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help
> pfcsig
> > SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
> [EMAIL PROTECTED] HOSTED BY IIGG, INC. FOR HELP WITH LIST SERVE COMMANDS, ADDRESS
> A MESSAGE TO [EMAIL PROTECTED] WITH THE FOLLOWING MESSAGE: help pfcsig
> SEND ALL OTHER INQUIRES TO [EMAIL PROTECTED]
