Well I just frequently have that problem When I go in the backdoor (>R prompt) to modify a form the variables in my RMD/APP file is not there and my memory is bad so every time I must do a little bit of investigation. It would be thanksgiving not to have to that, but to go straight at the problem. I can certainly dream it but not yet do it
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Lawrence Lustig Sent: den 22 november 2002 17:08 To: [EMAIL PROTECTED] 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/
