I posted this to another forum (https://www.accessforums.net/showthread.php?t=89285 ) and someone (moke123 ) has given me an example file with code. And it took me a little while to get it going. Then a little while to figure out how it works. But I think I'm going to try to implement that...
Wow, thank you for that info. I'll have to look into that and see if I can figure out how to make that happen. Thanks for pointing me in the right direction.
Hello. Is there's a way to set up a cell (used as a signature box) in Access to take in a secret code (per user) that gets matched up with their corresponding signature (initials)? Example, Mike Smith can't just enter MS. He would enter his code 5XR4T when he does MS will appear in the signature...
Wow! Thank you for your help! It must have taken a lot to go through it like that, and then to fix those issues on top of it. I have a lot to learn. I'm going to open it up, look into it, and carry thought with what you recommend right away. Thank you!
OK. Here it is. If you open Job_FRM, create a new job within there. Then click on the Shipment Received form via the button (open ship received), then try to enter anything into that form, you'll get that error. The Shipment Received form is the one that I've entered the code you recommended...
Hello Pat. Your recommendation is very much appreciated. It appears to be a much better solution than the one that I've concocted. However, I can't get it to run.
I've started with the first form, whose data source is the shipRECtbl table. And this table has the jobIDfk field that I need to be...
Thank you for that suggestion. When I entered/replaced the command with that one it's not working. Maybe because there hasn't been a record for the job created yet in the referenced tables?
Hello Doc. That is a very interesting analysis of this database. I'll have to experiment with the idea of the FK being the PK in those extra fields. Thank you for your help, and your balanced opinion. I'll keep you updated. Thanks again.
Hello Pat. Thank you for your warning and your recommendation. I will soon look into implementing it. I'll update with the progress made. Thanks again.
Hello Doc. There are no 1 to 1 relationships. Although I did think about it briefly.
As far as checking for duplicates upon creation of new records, with that field getting populated, I just changed the index property of that very field to "yes, no duplicates". That's working great.
So...
But, is there a way to prevent the error pop ups? So that the command just doesn't run if there are duplicates, and the user doesn't get confused by pop up error messages?
OK, I've found this info and it seems to have fixed that duplicate problem:
You can prevent duplicate values in a field in an Access table by creating a unique index. A unique index is an index that requires that each value of the indexed field is unique.
There are two basic ways that you can...
Hello Doc. Thank you. In the meantime I have tried something along those lines:
Private Sub Command18_Click()
DoCmd.RunSQL "INSERT INTO shipRECtbl(jobIDfk) VALUES ('" & Me.JOB_ID & "' );"
End Sub
I created an action button on the screen to create new jobs. And it doesn't do anything if I run it...