Let's see some design screenshots.

Additional info that might be relevant
Master form record source: SELECT DelicaProjectID, DelicaProjectT.BeadTypeID, DelicaProjectT.ProjectName FROM DelicaProjectT WHERE (((DelicaProjectT.BeadTypeID)=[Forms]![DelicaBeadF]![BeadTypeID].[Value])) ORDER BY DelicaProjectT.ProjectName;

Subform record source: SELECT DelicaProjectPictureT.*
FROM DelicaProjectT INNER JOIN DelicaProjectPictureT ON DelicaProjectT.DelicaProjectID = DelicaProjectPictureT.DelicaProjectID
WHERE (((DelicaProjectPictureT.DelicaProjectID)=[Forms]![DelicaBeadF]![SubformControl].[Form]![ProjectNameCombo]));

I think you may be running into a couple of classic Access issues at the same time. First, your parent form appears to be unbound (your controls show "Unbound"), which means there is no current parent record for the subform to link to. When that happens, Access will often reuse an old value, which would explain why new records keep defaulting to ProjectID 65. The subform really needs to be linked to a control on the parent form that actually contains the DelicaProjectID value, usually a textbox (it can be hidden), not just a combo showing a name.

Second, your WHERE clause is referencing controls on other forms and subforms, including something called "SubformControl," which is not a reserved name and must exactly match the name of the subform control on the parent form. That, combined with referencing a combo that appears to display a project name instead of the numeric ID, can easily cause Access to pull the wrong value.

As a first troubleshooting step, I'd simplify things: put the selected DelicaProjectID directly on the parent form, link the subform using Link Master/Child Fields only, and temporarily remove the cross-form WHERE clause. If that fixes the issue, you'll know the problem is the linking and filtering logic rather than the data itself.

SUCCESS!!!!!!! This thing has had me questioning if I've ever known a thing about Access. That Developer badge don't mean much when I'm still working my way through the Expert classes.
I made a new query concatenating the project type and name and made a new combo box in the form header to filter the detail section. Pics just 'cause I'm soooo happy!

Good job, I'm glad you figured it out. And yeah, the developer badge just means that you've purchased the developer courses. It doesn't necessarily mean that you've watched them. That's actually something that's on my list for an upgrade to the website is I want to make it so that you only get the badge when you've watched the videos on that course. So that's a whole different set of data to work through. But it's coming.

I started the badge system mostly so the moderators and I can get an idea for what kind of answer to give people in the forums. Obviously we'll give someone a different answer if we know they're only in the beginner lessons vs if we know they're up to developer 20. So that's just a quick way to say, "Okay, I can give this person a more advanced answer or point them to a more advanced class."