Gentlemen,
Thank you for your insight. Even though we are out here in force working on our RB7 apps, sometimes it feels like I may have made a wrong turn on a dark lonely country road. I guess the 200+ forms/reports is not going to be any more of a hit than moving the necessary rows/blocks of data over the network from the various tables in my app. It's probably old school mentality. Make your application and data base design as large and complex as necessary, but no bigger.
Dennis *****
At 05:55 PM 12/1/2004 -0800, you wrote:
Please consider the following to be nothing more than my opinion.
> 1. I have moved virtual all of my code in snippets to objects in the Design
> Menu Bar option. It's clean, sometimes redundant, but certainly makes
> debugging easier.
In my book, redundant is always bad. Usually when I say "just this once" it comes back to bite me in a week or two. Move that redundant code somewhere it does not need to be repeated -- a disk file, stored procedure, or RUN SELECT table.
> 3. And LBNL (for this email) I have moved a lot more data validation into > my forms and it would seem that I can remove a "shipload" of constraints.
Why remove the constraints? There are plenty of other ways that data can get
into your database (direct table editing, R:PHP, or whatever) and if those
constraints are part of the data model why not establish them once and let
R:Base enforce them in all cases, regardless of how the data is being or when.
I look on constraints as a opportunity to remove excess code, not the other way
around.
--
Larry
Dennis Fleming IISCO http://www.TheBestCMMS.com Phone: 570 775-7593 Mobile: 570 351-5290
