Often we create new assemblies or products using existing assemblies or products then editing the information in a created table. The code below is an example of the created table with the FK references. These are to mimic an existing table that has FKs in the first two columns just like the created tables. The only purpose of the table is to add, subtract or update parts that make up the assembly. Then this info is added to the permanent table.
CREATE TABLE &vnewtbl (`Assynumber` TEXT (20) REFERENCES partinfo (partnum) NOT NULL, + `Numpart` TEXT (20) REFERENCES partinfo (partnum) NOT NULL, + `AssypcsAE` INTEGER, + `Non_assyAE` TEXT (4)) Sometimes the user will add a bad part or assembly number. That is why I have the references in this table. The error message comes up as it should. The user deletes the bad info then continues through the process and inserts the good info into the permanent table. The above table is then dropped. However in two instances, one last week and one this week, though the error message did what it was supposed to do, the code also messed up my SYS_COMMENTS table and made the DB unavailable. I had to get everyone out, fixed the SYS_COMMENTS Table and then we were okay. Can anyone see if my code is bad? I just implemented this. James Belisle Making Information Systems People Friendly Since 1990 [cid:[email protected]] -- For group guidelines, visit http://www.rbase.com/support/usersgroup_guidelines.php --- You received this message because you are subscribed to the Google Groups "RBASE-L" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rbase-l/DM6PR02MB45399132083220C99091A2A5A0AC0%40DM6PR02MB4539.namprd02.prod.outlook.com.
