Form that updates/adds to part of database

[mike60smart]

Hi

Your linking of Subforms was incorrect.

You do not need to make a Reference to the Main Form in the Record Source of the Subform.

All you need to do is make sure that you have included the linking FK

You will find that the attached is now linked correctly.

View attachment Crocs.zip

 

[Pat Hartman]

I fixed it. Somehow the master/child link got broken after I tested the form.

 

[Sharkman1885]

Thanks Pat,
Im still not sure where State ID came from.

Mike,
Thanks for the upload. I am trying both out today and will try to get it to do what I want. Thank you guys and I do apologize about my late reply

 

[Sharkman1885]

Pat,
It appears as though the DoO (Date of Occurrence) is not being associated with the biological info for the croc. basically if a croc is caught in location A with a length of 100cm in February and the same croc is handled two months later at location B and a length of 105cm...the two dates need to jive with the different measurements and locations. That doesnt seem to be happening currently

 

[Pat Hartman]

Please repost the database so I can see what you see. Compact and zip to save space.

 

[Sharkman1885]

Pat,
Under the ID tab there is a text box called "State ID" and I have no clue where that came from. I have also added an add croc button to add new animals to the database. When there is a new encounter, such as a new date and location, but it is for the same animal, the Location ID does not change and all the biological data is saved under one location ID. So for instance if the same croc is handled multiple times over the course of 2 years in different locations, The location and time data is lost when adding in the new time and location.

 

[Beetle]

Here's an alternative example of how to model this based on my previous advice that you have a many-to-many relationship between Crocs and Encounters. To be more specific, in this example, the M2M is between Crocs and Locations, with tblEncounters being the junction table that manages the relationship. A couple things to keep in mind.

1) This is very generic so it would likely need some modification to work for your specific scenario

2) I don't have a clear picture of how your Other Info table should relate to the rest of the data. In this example I related it to Location data, but it may actually relate to one of the other entites.

 

[Pat Hartman]

Sharkman,
I am not going to fight with Beetle over your data model. I agree that it is still confused. Beyond that, I can't keep rebuilding the app for you. My original model had Encounter separate from location so there would be a m-m between croc and location and that would be called encounter. Somehow that got changed.

It is really not possible to build forms until the schema is sound and it is not yet sound. In addition to the location/encounter issue we still have the croc/id confusion. Beetle has things connecting to Croc and I believe everything needs to connect to "ID".

So I'm done unless you want me to continue. Good luck.

 

[Beetle]

See how I am? I said I wouldn't confuse the issue and then I went and confused the issue;-)

If Pat's original example was structured m-m and then you changed that for some reason, then that may be the root of why you are struggling to get the forms to work the way you need. Pat has more time and effort into your project than I do, plus a lot more experience in general, so I would say continue down the path you already started and I will drop out (really, I swear this time).