Comments on: Made2Manage Lacks Referential Integrity

By: That’s Quite a View – INMast | Made2Mentor

That’s Quite a View – INMast | Made2Mentor — Wed, 17 Feb 2010 17:48:28 +0000

[...] take the opportunity to normalize the database (or at least significant portions of it) and enforce referential integrity while migrating to the .Net platform. I think they should drop VFP entirely, train users to use SQL [...]

By: Orphaned Records and Technical Hypochondria | Made2Mentor

Orphaned Records and Technical Hypochondria | Made2Mentor — Fri, 05 Feb 2010 01:46:00 +0000

[...] table with an order by clause. Once again, this occurs because in my opinion the M2M database is not properly designed. Here’s a quick walk-through on how I found it. Incidentally, the screen shots are from TOAD [...]

By: David

David — Wed, 26 Aug 2009 04:19:06 +0000

Just today I had to call support because I had a duplicate record in the Job Order Master Table (JOMAST). These kinds of problems should not occur in a properly designed SQL database.

By: Brent Ozar

Brent Ozar — Tue, 25 Aug 2009 12:44:24 +0000

Good post! I’ve heard people say that adding referential integrity inside the database slows the database server down, but hey, so does adding data. I love having double-checks inside the database engine to prevent something truly bad from happening. Programs have bugs, and adding referential integrity inside the database server is like Reagan’s quote: “Trust, but verify.”

By: Jason Griffith

Jason Griffith — Mon, 24 Aug 2009 15:43:06 +0000

Orphaned records are something I run into no matter what form of database system we’re talking about. I do notice quite a bit in M2M, but I have seen much worse with other systems.

Consona’s apparent focus on short term rather than long term is likely due to the code they are using. Would you want to put a serious amount of effort into robust VFP code? I certainly wouldn’t. That sorry language should have died a long time ago. Oh wait, it did die a long time ago….It’s really more valuable for them to give short term fixes and quick new releases than it is to devote the time/effort/money into developing robust code for the Latin of programming languages.

I have hopes (not too high, of course) that the .NET version will have a more solid and robust foundation that what we have right now.

By: scott

scott — Mon, 24 Aug 2009 14:36:49 +0000

I have on several ocasions found orphan records. In fact M2M support often has me check for these when I run into issues.

While I agree that refriential integrety should exists, it is my guess that M2M is more concerned with issues and features that have a more direct pay back. Thier overall pholosify seems to be to write quick and dirty code rather then to spend the time and effert necessary for robust code. While there method is best for the short term, they don’t seem to realize the long term benifits of robust code.