Search results

Believe it or not - I now have that part figured out. So proud of myself. :-) I'm able to input a new coil with no record in tblCoils, open frmCoilStatus and enter all the relevant data, save, close return to frmInspectMill and have the new coil recorded in tblCoils and also brought the coil ID...

So now I have managed to pass my new value from a bound textbox on Form2 back to an unbound textbox on Form1 and Form2 closes because I am done with it. Now that the unbound textbox on Form1 has a value in it - I need to click a "Save and Close" button on Form 1 to record all of the data I have...

Ok - so a simple form.control reference did the trick. I think I'm almost there.

I've been searching but haven't found it. Do you have a link? Thanks! Tim

and.............after another marathon day..........I almost have my situation figured out! But--------the last piece of the puzzle. If I have two open forms, is there a way to pass a value from a textbox on the form I am working on (Form1) to a textbox on Form2 (which is already open) when I...

We made it through the hail! Yeah! So.......................... :) Almost - you almost have it! But NOT Only SOME types of inspections are "performed on coil samples in jobs." Mill and Line Stop inspections = YES (always); Welding, Fabricating, Painting, and everything else types of...

Is the primary issue that I have included tblInspectionEvents.InspectionNotes on frmInspectMill? My thinking was that I need a notes field for all types of inspections and I was considering normalization of a notes field to tblInspectionEvents instead of each inspecion table having its own notes...

What can I provide to clarify business rules? Also - I may be offline soon - -the weather just called for golf ball-size hail and a possible tornado in the next half hour. Never a dull moment. :-)

That is why I thought it might be helpful to look at the SQL in post #47 because it kind of spells out how tables are related to each other. and what is drawn from each.

Are you beginning your "tests" at the very beginning from Main Menu and clicking on the "Inspections" button every time? Because.....all inspections begin there. The first step (and unavoidable required step) is choosing a job in frmInspectionEvent before selecting which type of inspection you...

I did the same. ...and have the same question. Because in fact, there are several fields that are most easily recorded at the mill. What do you think necessary logic is? I am hoping there is a way to open something similar to frmCoilStatus to fill in several more required fields at the time...

Actually - I think you should remove existing logic to see what needs to be removed to get it to work. That would be quite telling I think.

I'm getting closer. I took the "Debug.Print" out of the CurrentDb.Execute statement and it worked - kind of. Then I entered a non-existent coil number in txtCoilNumber. When I moved the focus off of txtCoilNumber the frmInspectMill closed and reopened but it did not have the coil number placed...

Not that I'm shocked - but my coding appears sloppy - lol. I just made txtboxes for InspectionEvent_PK on frmInspectionEvent and InspectionEvent_FK on frmInspectMill visible and commented out the line of code in the On Load event of frmChooseComponent so I can see if the id gets passed from...

Understood. I was just thinking that "purpose" might help explain structure.

intInspID is a global variable. It worked fine until I started messing with trying to change that cbo to have a blank field.

I just posted Coil Question 4.zip which is updated to include your code modified to reflect control names and also includes a query that may help make more sense of what I am ultimately trying to accomplish. When looking at your screenshot of the immediate window - and if I am accurately...

I don't know if it will help or not but attached is the db with a button added to the Main Menu called Example Query. Maybe seeing an example of what I'll be looking for in a report will help clarify? Here's the SQL for it: SELECT tblinspectionevent.datetime, [jobnumber] & [task] &...

Yes - that is correct. Currently Jobs and Coils are related ultimately through tblInspectionEvent which acts a junction table of sorts between tblJobs (always) and the various types of inspections (mill inspections sometimes). Maybe what is not clear is that a given coil can very often be an...

Every word of this quote is exactly the issue I'm facing. I'd prefer to have it all on one form but it clearly makes it far too compllicated for my simple mind with little time. :) On the other hand - - I *could* (and I believe I already know how to ) strip my existing "frmCoilStatus" form...