relationships needed?

Dear experts -
Sorry for the provocative title!
I was having major issues with cascading deletes in a form, so I made some changes to the recordset as well as removed ALL relational integrity enforcement/cascading deletes in the Relationships setup for the back-end.
The problem is gone.
However, I'm wondering now about the macro questions - do I need the Relational Integrity checking? Can you have a good relational database in Access just using the native forms/subforms without it?
Can you please lay out the arguments pro/con?
I know it's both a basic and a big question.
Thanks so much -
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Can you have a good relational database in Access just using the native forms/subforms without it?
No, you can't have a good relational DB without enforcing the constraints.
You might have a satisfactory relational db, but if your database complexity will increase in time, you will end up with a total mess, aka orphaned rows, partially missing data etc..
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
So you removed the relationships, or you removed the Cascade Delete/Update enforcement on the relationship?

IMO Cascade Update and Delete are useless in a properly designed database.

That said: You must enforce constraints as some level. Whether that level is at database engine or at code level is up to you. I've built plenty of simple databases with no referential integrity at the engine level, but it was definitely more work to insure I had valid data in my foreign key fields. All in all, I think you're probably better off enforcing referential integrity at the engine level, but NOT enforcing Cascade Updates or Deletes.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
terpsichoreAuthor Commented:
Thanks - this was the level of detail I was looking for. I reinstated just the referential integrity. (Indeed, we are enforcing the relationships - the structure is properly normalized - through code, e.g., through the subform key-field linkage, which has served us well to date.)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.