Maybe I'm putting the Cart before the horse but....Relationships.
I'm using unbound forms with mostly SQL statements behind them, do I still
need to define the relationships between tables, and if so why?
Thanks
DS
To be honest, I don't see what difference it makes that you're using unbound
forms and SQL statements.
To me, a major reason to use relationships is to enforce referential
integrity.
Remember that it's possible for others to use your data without using your
forms.

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
> Maybe I'm putting the Cart before the horse but....Relationships.
> I'm using unbound forms with mostly SQL statements behind them, do I still
> need to define the relationships between tables, and if so why?
> Thanks
> DS
DS - 31 Mar 2007 17:27 GMT
Thanks Douglas, that clears things up a bit! So when you say referential
integrity, do you mean that a record can't be entered on any without having
entered the main record first? Would this matter with the SQL statements
since its pretty well controled?
Thanks
DS
> To be honest, I don't see what difference it makes that you're using
> unbound forms and SQL statements.
[quoted text clipped - 10 lines]
>> Thanks
>> DS
Douglas J. Steele - 31 Mar 2007 18:14 GMT
In addition to preventing inappropriate entries from being made, RI can
provide (should you want) cascade deletes or cascade updates.
As I stated before, remember that it's always possible for others to use
your data without using your forms. The more you can do to protect the
integrity of the data, the better.

Signature
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no private e-mails, please)
> Thanks Douglas, that clears things up a bit! So when you say referential
> integrity, do you mean that a record can't be entered on any without
[quoted text clipped - 16 lines]
>>> Thanks
>>> DS