Search results

  1. O

    Relationship Issues

    I started over using yours for a model and added in some of the other suggestions from here. I decided a few of the other bits could be included in the normalization. If I am off track or missed anything, please feel free to correct me. I really appreciate your help.
  2. O

    Relationship Issues

    Thank you GPGeorge. I will try it out. I really appreciate it. I have a question. On the frmInput on the one you corrected, in the Lead tab, it is skipping rows. There is data in PK055 and PK057, but not PK056. On the Asbestos tab, there are no skipped spaces. Is there a way to correct that?
  3. O

    Relationship Issues

    Thank you GP. Yes, they are both names. However the names are or can be different depending on the type of test. So each type of test can have a different value.
  4. O

    Relationship Issues

    This is what I currently have with one table and the data above.
  5. O

    Relationship Issues

    Examples of Data tblAsset Unit - 1001 AssetID CU01P003 AssetType Equipment tblSample LeadFor Bill LeadGroup Maint LeadSampleID PB 091922BS-05 LeadSampleDate 9/19/2022 LeadAbater Acme LeadMatColor Red LWO...
  6. O

    Relationship Issues

    The tests are actually 3 different entities. The only thing they have in common all the time is the data from tblAsset - Unit, AssetID and AssetType. I am using one table now.
  7. O

    Relationship Issues

    LeadFor and AsbestosFor are people's names. They will not be the same for both - any one of 100 and constantly changing. Or might be. One Asset can have multiple tests of each type over several months for different people. Abater is the group doing the testing. A company name. They come and...
  8. O

    Relationship Issues

    No, it is different data going into different fields. For example, there is a LeadFor and an AsbestosFor - they are different fields and may or may not be the same data. They are different fields because they are different types of tests.
  9. O

    Relationship Issues

    Dawn just broke over Marble Head. One table is working fine. And now my query works.
  10. O

    Relationship Issues

    I tried one table. The two types of tests have similar data, but there are some differences. The results are different. The Abater may be different for Lead than it was for Asbestos. The dates will be different for each. The Group and For may be different for each. The Sample IDs and...
  11. O

    Relationship Issues

    Understood, it won't happen again.
  12. O

    Relationship Issues

    AssetIDFK=1 does not have an asbestos sample, it only has Lead right now. Not every asset has all three. tblLeadSample and tblAsbestosSample have very similar structure, but they are not exactly the same. The results are reported differently. And some assets will have one, some will have two...
  13. O

    Bill's Introduction

    Understood. It won't happen again.
  14. O

    Bill's Introduction

    Understood. I thought they were two separate forums.
  15. O

    Relationship Issues

    Thank you very, very much for your help.
  16. O

    Relationship Issues

    Thanks plog. The parent/child relationship was wrong on the two that weren't working. It is working like a champ now. You guys are geniuses!
  17. O

    Bill's Introduction

    Thank you and thank you for the help. There was mention of crossposting in my thread, is that not appropriate?
  18. O

    Relationship Issues

    This is what I have. I used a Tab Control on the Main Form frmInput and dragged the subs on to each tab.
  19. O

    Relationship Issues

    1. I tried to put it in and this time it took it, but it also copied the same information to the Lead Tab. They need to be distinct. 2. No, I didn't copy it. I built it from scratch.
  20. O

    Relationship Issues

    Here is the PK the lead is pulling from and the ASB won't.
Back
Top Bottom