joins in jet/mdb vs. joins in adp/SQL server

[scroce]

need some clarification:

In jet mdb, you can go into relationships, join a pk with a fk, and then you hit a button called "join type", which gives you the choice of assigning type 1, 2 or 3 (i guess corresponding to INNER, RIGHT OUTER and LEFT OUTER)

Diagrams in SQL server doesn't seem to have the same thing. Is there a way to do this in SQL Server, or is the concept different? Maybe you only invoke the join type when writing SQL code?



I am a nobody, and nobody is perfect; therefore, I am perfect.

 

[danvlas]

Right-click the join line. It's all in there, and even more (the full outer join, which does not exist in Access)

HTH


Daniel Vlas
Systems Consultant

http://www.geocities.com/danvlas/AutoMail.html

 

[scroce]

I must be missing something, I did this, and chose properties, which shows me a screen with table, columns, relationships, indexes/keys, check constraints

I see cascade update and delete, but no join types. what am i missing?

I am a nobody, and nobody is perfect; therefore, I am perfect.

 

[cmmrfrds]

What is the requirement to try and preset Joins in the SQL Server tables?

 

[scroce]

yes - is this done the same way as it is in Jet?

I am a nobody, and nobody is perfect; therefore, I am perfect.

 

[cmmrfrds]

I believe the reason Jet allows preset joins is so that Access can take defaults when the User is building queries in the QBE and maybe some other default processing. This would not apply in an ADP.

 

[scroce]

so then you are saying that you can still do joins, but not default ones, like in MDB - if you want those, then you just have to write them into your SQL statement.

right?

I am a nobody, and nobody is perfect; therefore, I am perfect.

 

[cmmrfrds]

Yes, the joins are coded by you in the SQL Statement.

 

[scroce]

OK - thanks! that helps!

I am a nobody, and nobody is perfect; therefore, I am perfect.