Page 2 of 2 FirstFirst 12
Results 16 to 18 of 18
  1. #16
    kd2017 is offline Well, I tried at least.
    Windows 10 Access 2016
    Join Date
    Jul 2017
    Posts
    1,142
    No, they are not the same data. Though, they would be of the same unit.



    Measurement.measured_qty would be an actual measurement
    Assembly.measured_qty should be something more like 'a quantity in the measured quantity's units'.
    24 ft and 1.33 ft respectively in the original example.

    BUT these were just placeholders for this question. There's a whole series of related tables where I would be looking to apply a naming convention for successive ratios like this. Hence the need for a consistent convention.

    [edit]
    It occurs to me I'm essentially modeling the 'railroad track method' for unit conversion.
    Last edited by kd2017; 03-17-2023 at 10:50 PM.

  2. #17
    Edgar is offline Competent Performer
    Windows 8 Access 2016
    Join Date
    Dec 2022
    Posts
    271
    Quote Originally Posted by kd2017 View Post
    It occurs to me I'm essentially modeling the 'railroad track method' for unit conversion.
    Read about price analysis in construction, I gave you a digested break down in post #11. It's a proven method and that comes from someone in the field. That's how we estimate stuff. You basically analyze how much material is necessary for 1 parent unit using any number of rows in the child table. These rows will be simply multiplied by parent quantity and you will have a total. You want names? You can use yield, coverage, coverage rate, material efficiency, material yield, material usage, material consumption. I don't understand why you want to give a field name for number 1 (your numerator), it's always going to be 1. It's one parent unit what you are measuring.

  3. #18
    kd2017 is offline Well, I tried at least.
    Windows 10 Access 2016
    Join Date
    Jul 2017
    Posts
    1,142
    Thanks Edgar. But I'm not asking how to do price analysis, I was brainstorming to establish a naming convention. And in fact the numerator will not always be one in this model, otherwise there would be no point to this.

Page 2 of 2 FirstFirst 12
Please reply to this thread with any new information or opinions.

Similar Threads

  1. Naming Convention for multi level organization
    By Tuckejam in forum Database Design
    Replies: 6
    Last Post: 04-20-2020, 02:32 AM
  2. Replies: 3
    Last Post: 11-13-2019, 04:30 PM
  3. The PK and FK field naming convention....
    By DBID10T in forum Database Design
    Replies: 6
    Last Post: 10-25-2019, 05:49 AM
  4. Naming convention question? btn or cmd?
    By RLehrbass in forum Access
    Replies: 7
    Last Post: 09-21-2015, 07:51 PM
  5. I use my own VBA naming "convention"
    By keviny04 in forum Modules
    Replies: 13
    Last Post: 06-05-2015, 03:09 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums