Go Back   Access World Forums > Microsoft Access Discussion > Theory and practice of database design

 
Reply
 
Thread Tools Rate Thread Display Modes
Old 11-19-2019, 08:17 AM   #31
JoeBruce
Newly Registered User
 
Join Date: Jan 2017
Posts: 29
Thanks: 8
Thanked 0 Times in 0 Posts
JoeBruce is on a distinguished road
Re: Normalizing (and fixing) a large, messy DB

Thanks for the quick reply, plog. I read it the other day and have been pondering your advice.

To answer your main follow up question, permits relate to the climbers who climbed and which routes they climbed. A permit can relate to a guide company, but only if one was present for the climb (in the context of data, that means a null value should be acceptable here). I might play around with the idea of a guide company relating to tblRouteRecords, especially in the context of your forms advice.

What you wrote about forms makes a lot of sense. I have done something similar, just not in the order you describe. I will experiment a bit and see what I can come up with.

I've realized the issue with forms based on queries; I generally use tables too, but when looking at the record set for the form I guess I turned it into a query. I had been referencing the other database I made, and saw that main form used a query. Now looking closer I do not think that form pulls data from more than one table, so the query there is superfluous. For this database, I've reverted back to the form based on a table; my subforms all seem to be select queries, though.


Last edited by JoeBruce; 11-19-2019 at 08:45 AM.
JoeBruce is offline   Reply With Quote
Old 12-07-2019, 01:07 PM   #32
gemma-the-husky
Super Moderator
 
gemma-the-husky's Avatar
 
Join Date: Sep 2006
Location: UK
Posts: 13,830
Thanks: 56
Thanked 1,032 Times in 998 Posts
gemma-the-husky is a name known to all gemma-the-husky is a name known to all gemma-the-husky is a name known to all gemma-the-husky is a name known to all gemma-the-husky is a name known to all gemma-the-husky is a name known to all
Re: Normalizing (and fixing) a large, messy DB

Out of interest, do you know how much your firm spent on the database.
How many forms are there? How many queries?

Re-engineering a large database is an extensive and difficult project. Re-engineering a bad database is hard to justify. You may as well start over, but you have to convince someone that it's worth the effort and cost.

__________________
Dave (Male!)
Gemma was my dog

if a poster helps you, please click the scales at the bottom left of this posting, or use the thanks button alongside.
gemma-the-husky is offline   Reply With Quote
Reply

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Scattered fields make a messy table hilian Tables 16 07-10-2015 11:22 AM
A very messy Count. pr2-eugin Queries 2 01-03-2013 06:22 AM
Import from Excel - Messy maw230 General 10 08-05-2010 10:29 AM
[SOLVED] VBA routine that would organise my messy table kalevi12 Modules & VBA 3 04-03-2006 04:23 AM
messy screen during runtime striker Modules & VBA 1 05-09-2002 01:00 AM




All times are GMT -8. The time now is 04:55 AM.


Microsoft Access Help
General
Tables
Queries
Forms
Reports
Macros
Modules & VBA
Theory & Practice
Access FAQs
Code Repository
Sample Databases
Video Tutorials

Featured Forum post


Sponsored Links


Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
(c) copyright 2017 Access World