Karen, That is what I did this am. I was testing it out because I was getting junk into a couple of my tables. The check should care for that, however. Thanks for the suggestion.
James Belisle Making Information Systems People Friendly Since 1990 [cid:[email protected]] From: 'Karen Tellef' via RBASE-L [mailto:[email protected]] Sent: Tuesday, August 6, 2019 7:57 AM To: [email protected] Subject: Re: [RBASE-L] - internal lock Hmmm... don't know if that's a problem or not, but I would mention that I don't think I have ever once used an FK on a temp table. Try removing it and just use a manual check of the data before adding it to the perm table? Karen -----Original Message----- From: Jim Belisle <[email protected]> To: [email protected] <[email protected]> Sent: Mon, Aug 5, 2019 5:25 pm Subject: [RBASE-L] - internal lock When creating new products I use an existing product, edit the parts used in the new product in a TEMP table then insert the new product and parts into the proper tables. In order to make sure I am not inserting bad parts (parts not in the system yet) I over the weekend add a FK to the temp table on the parts column in the temp table and also made it not null. This worked fine with no problems when I tested this on my backup DB on my local drive. However when using this method today on the server, I ran into an internal lock situation when running the code. Is it not wise to use FKs for temp tables created on the fly? I have not run into this before. 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]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/rbase-l/DM6PR02MB45393FD249866BFDE6132D32A0DA0%40DM6PR02MB4539.namprd02.prod.outlook.com<https://groups.google.com/d/msgid/rbase-l/DM6PR02MB45393FD249866BFDE6132D32A0DA0%40DM6PR02MB4539.namprd02.prod.outlook.com?utm_medium=email&utm_source=footer>. -- 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]<mailto:[email protected]>. To view this discussion on the web visit https://groups.google.com/d/msgid/rbase-l/922514639.1731411.1565096216819%40mail.yahoo.com<https://groups.google.com/d/msgid/rbase-l/922514639.1731411.1565096216819%40mail.yahoo.com?utm_medium=email&utm_source=footer>. ________________________________ -- 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/DM6PR02MB45392D7B7DE3F8A6AA4A3E45A0D50%40DM6PR02MB4539.namprd02.prod.outlook.com.
