Hello, I'm migrating an Access-DB to Sap-DB and now I have a problem with some appearant special features of Access which were really useful at the beginning. I will try to explain my problem on the basis of an example: I have 4 tables: - Inquiry (inq_Number as serial (primary key),..., inq_customer as string) - Parts (Part_description as string, inq_Number, part_number as serial (primary key), .., user as string) - User (user_number as serial (primary key), user as string, department_nr as integer) - Departments (department_nr as integer (primary key), departement_name as String)
At Access I have the following relationships: Case 1: Inquiry.inq_number <-> Parts.inq_number (referential with delete option -> no problem) Case 2: Parts.User <-> User.user (relationship without referential constraint) Case 3: User.department_nr <-> Departments.department_nr (relationship with referential constraint, but no delete rule, only "Aktualisierungsweitergabe", which means, if I change the department_name it will be passed on to the user table, because Access knows the "bound column" (the relationship is realized through the department number, but at the user table there will be shown the department name)). Here are now my questions: 1. Can I create a (foreign key) relationship between two tables like case 2? Without referential constraint means that if a part is deleted the user will never be deleted, even if this user only used this part. 2. Is there a way to realize bound columns? 3. What if I define no delete rule and the value at the referenced table (Table 2) is not at the referencing table (Table 1), but at another table (Table 3), which itself has a referential constraint rule with Table 2. Will the Value at Table 2 be deleted or not (it's the 'matching row' and 'Reference Cyle' I don't really understand). I hope I made it clear where my problems are. Thanks in advance Peter Huebschen _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
