Need to set Access Relationships when using ASP?

[crispy]

This is something that I am never completely sure about:

When building an Access db to be accessed by ASP, do I need to worry
about setting the Relationships between the tables and the Join Types
(one to many ,etc.), or can I just rely on declaring the relationships
in my SQL statements?

How about the setting for Referential Integrity. Should I ever have to
worry about having Access enforce those, including update and deleted
related records?

I have never bothered with setting the relationships in the couple of
simple databases I've built for ASP. But I always wonder if I should
do that.

Thanks in advance,

crispy

[Bob Barrows [MVP]]

crispy wrote:

This is something that I am never completely sure about:

When building an Access db to be accessed by ASP, do I need to worry
about setting the Relationships between the tables and the Join Types
(one to many ,etc.), or can I just rely on declaring the relationships
in my SQL statements?

How about the setting for Referential Integrity. Should I ever have to
worry about having Access enforce those, including update and deleted
related records?

I have never bothered with setting the relationships in the couple of
simple databases I've built for ASP. But I always wonder if I should
do that.

Thanks in advance,

crispy

Do a Google in the Access newsgroups. You'll find a lot of opinions.
Personally, I think it's important to set up referential integrity via
Relationships because you cannot guarantee that your asp app will be the
sole means used to modify data in that database.

Bob Barrows
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.