Circular links in database design. Should they be avoided?

Question

I am currently developing a database through MS Access 2003 and am stuck in a circular reference issue. Basically, it comes down to the following relationship triangle (this is a simplified form of my relationship table):

                     Positions
                 oo            oo
                /                \
               /                  \
              /                    \
             /                      \
            /                        \
           /                          \
          /                            \
         /                              \
        /                                \
       /                                  \
      oo                                  oo
  Employees  oo -------------------- oo Software,

where Positions, Employees and Software are tables, and "oo-------...-------oo"displays the relationship between them to many.

, ( ) () (). , , , .

, ? - , ?

, VS.

Answer 1

, N: N . . 1: N CASCADE DELETE on . N: N , CASCADE DELETE " " 1 N, N: N .

, , , , @Saif Khan - , . , , - , - ( ), /, UNION. , , , .

A2010 Access/Jet/ACE, A2010 , . , .

, , .

Answer 2

, . , .

Answer 3

. . .

• EmployeeSoftware

"POSITIONS" , , . , , -. , ,...

Employee EmployeeSoftware (empid EmployeeSoftware. Software EmployeeSoftware (softid EmployeeSoftware.

, (POSITIONS) . EmployeeSoftware POSITIONS ... .

Answer 4

, - ,

" , , ().

.

, - . , , .

. --, , , .