Might the GLOBAL nature of such SYS_VARIABLES be a problem with multi-user situations? If I remember correctly, the original problem was a view with variables in the where clause. Different users may well want different values. If the variables are just defined and start with null values then I would not be concerned.
----- Original Message ----- From: "David M. Blocker" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, November 22, 2002 1:35 AM Subject: Re: Labels > Submit it Larry!! > > David > > ----- Original Message ----- > From: "Lawrence Lustig" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, November 22, 2002 11:07 AM > Subject: Re: Labels > > > > > Feedback anyone? > > > > I would make two (mutually exclusive) suggestions: > > > > 1. Your idea of static variables be maintained in a SYS_VARIABLES table so > > that they could be queried and manipulated with SQL. > > > > 2. That a bunch of additional trigger opportunities be added: > > > > ON_CONNECT > > ON_DISCONNECT > > ON_MODIFY_FORM > > ON_SAVE_FORM > > ON_MODIFY_REPORT > > ON_SAVE_REPORT > > > > This would let you add some code to ensure that, whenever you change a > form > > or report you create the necessary variables when bringing up the > designer. > > -- > > Larry > > > > > > ================================================ > > TO SEE MESSAGE POSTING GUIDELINES: > > Send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: INTRO rbase-l > > ================================================ > > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > > In the message body, put just two words: UNSUBSCRIBE rbase-l > > ================================================ > > TO SEARCH ARCHIVES: > > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > > > > > ================================================ > TO SEE MESSAGE POSTING GUIDELINES: > Send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: INTRO rbase-l > ================================================ > TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] > In the message body, put just two words: UNSUBSCRIBE rbase-l > ================================================ > TO SEARCH ARCHIVES: > http://www.mail-archive.com/rbase-l%40sonetmail.com/ > ================================================ TO SEE MESSAGE POSTING GUIDELINES: Send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: INTRO rbase-l ================================================ TO UNSUBSCRIBE: send a plain text email to [EMAIL PROTECTED] In the message body, put just two words: UNSUBSCRIBE rbase-l ================================================ TO SEARCH ARCHIVES: http://www.mail-archive.com/rbase-l%40sonetmail.com/
