Does the nature of your rules allow the use of constraints instead? Things
like uniqueness, etc. Another option that I have used is to do the checks
in code when you move the data to the permanent locations - verify the data
in the temporary table before you do anything and force the user to fix the
errors before the permanent changes are made.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Rommel Relosa
Sent: Monday, May 21, 2001 12:57 PM
To: [EMAIL PROTECTED]
Subject: Temporary Tables and Rules
Hello to all.
I was wondering if anyone can give some insight in regards to placing rules
on temporary tables.
The system application we have created opens the database with SET STATICDB
ON to prevent (mostly to stop the developers) structure changes while the
database is in use.
This setting however, doesn't stop us from using temporary tables (which was
a God-Send).
Now, here is my problem, I have code that creates temporary tables and as
soon as the tables are created, autonumbers and rules are added. This code
runs fine if it is run outside of a form.
The part of the code that creates the rules on the temporary tables issues a
message, "Illegal Entry/Exit Procedure."
Is the setting (SET STATICDB ON) hampering this rule creation? Or, in the
current version of R:Base, we just cannot add rules to temporary tables
inside an EEP?
If at all possible, I would like to keep the rules on these temporary tables
and right now, I have the tables created every time the program is executed
prior to opening any form. I would like to create these temporary tables
when the tables are needed, but, the circumstances would require to create
the temporary tables 2 - 3 forms into the application.
Thank you all for your time.
Rommel
