Results 1 to 3 of 3
  1. #1
    Join Date
    May 2017
    Posts
    2

    Lightbulb Unanswered: Break up tables based on values from another table

    Bear with me, I'm going to try and explain this as clearly as possible.

    Let's say I have two tables, A and B.
    A is a really, really big table, with lots of part numbers.
    B is a list of only SOME of those part numbers.

    Kind of like these:
    Click image for larger version. 

Name:	tABLE A.jpg 
Views:	2 
Size:	14.4 KB 
ID:	17353Click image for larger version. 

Name:	tABLE b.jpg 
Views:	1 
Size:	9.3 KB 
ID:	17354
    So, I want to break up Table A into a ton of separate tables, based on the values in Table B.
    Essentially, it would give me everything that's included under 1B in table A, UNTIL it hits 2B and then stop, and then repeat that process over and over until all has been broken apart.

    Any ideas please? This is a fairly hot item I'm working with. If anyone needs more clarification, please ask.
    Last edited by heath1056; 05-12-17 at 16:35.

  2. #2
    Join Date
    Apr 2014
    Location
    Kentucky
    Posts
    629
    Provided Answers: 33
    breaking up 1 table into many tables does not sound good. Breaking into 2 tables, a parent and child does.
    you dont want your data spread over lots of table where retrieval is a problem.

    create 2 make table queries and save the table so each has relatable keys.

  3. #3
    Join Date
    May 2017
    Posts
    2
    Quote Originally Posted by ranman256 View Post
    breaking up 1 table into many tables does not sound good. Breaking into 2 tables, a parent and child does.
    you dont want your data spread over lots of table where retrieval is a problem.

    create 2 make table queries and save the table so each has relatable keys.
    So how can I make table A have relatable keys from the values in table B?
    The end goal is to eventually have historical tables pieced back in together in table A, based on the values given from table B (1B, 2B) etc.
    So I would have a third table, for JUST table 2B data, that I would then insert into the slot allotted for table 2B.

    If Access is not the correct database tool to handle this, what is the best course of action? Would a SQL database handle data in this large quantities?

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •