- Local time
- Today, 15:37
- Joined
- Oct 29, 2018
- Messages
- 22,605
I guess at this point, we have no choice but to ask if you can post a sample copy of your db.Textbox has been changed when I updated the table. still same error.
I guess at this point, we have no choice but to ask if you can post a sample copy of your db.Textbox has been changed when I updated the table. still same error.
I will upload a copy later tonight. Appreciate the help!I guess at this point, we have no choice but to ask if you can post a sample copy of your db.
Just remember, Application has a special meaning in Access.I notice when I start to type Application on my new database it would populate and i could select Application_Name on my original it is not doing this.
Congratulations! Glad to hear you got it to work. I'll take a look at your file when I get back in front of a computer.I got it finally!!!!!!!!!! I had to delete and recreate the button and now it is working perfectly! Thank you for your help. Not to hijack my own thread but i do have a follow up question.
you will see in the test database I provided you will see my application list form has to fields number of incidents and most recent incident. I would like to populate these fields automatically when an incident is created in the incident library form. I would like number of incidents to show a count and most recent to display the date of the most recent incident for that specific application.
Congratulations! Glad to hear you got it to work. I'll take a look at your file when I get back in front of a computer.
Sent from phone...
Can you post the latest version of your db? It might help.I have noticed during testing if i have a record saved in the Incident Information field. Then go to a different application and click the button it is pulling over the correct application name but also the information that was entered previously for an application. Is there a way to make sure when I hit the button it is creating a new record and only populating the application name on the form?
Can you post the latest version of your db? It might help.
Okay, if the purpose of the button is to create "new" incidents, then try changing the button code to this:I have attached the db with some test information. If you notice when you go to the application list and click new incident it will populate the correct name but also prefill the rest of the fields with an incident that has been logged in the incident library table.
DoCmd.OpenForm "Incident Library", DataMode:=acFormAdd, OpenArgs:=Me.Application_Name
Okay, if the purpose of the button is to create "new" incidents, then try changing the button code to this:
Rich (BB code):DoCmd.OpenForm "Incident Library", DataMode:=acFormAdd, OpenArgs:=Me.Application_Name
Not exactly; and, be careful. You are about to commit a possible error in db design. Normally, two tables are related by using one field only. It's possible to use more fields in a relationship, but you'll have to explain your situation first, so we can tell if yours is an exception or not.That did it! Thanks!! If i wanted to have a similar button add 2 fields to a new form say Application Name and Incident number would i used the above code and just add a second openArgs?
Not exactly; and, be careful. You are about to commit a possible error in db design. Normally, two tables are related by using one field only. It's possible to use more fields in a relationship, but you'll have to explain your situation first, so we can tell if yours is an exception or not.
Hi. If you're talking about something like a "history" or "status updates" to an incident record, you might consider using a form/subform setup. The main form could be based on the incident record and the subform could be based on the "changes."What I would like to do is create another table and form that is for updating an ongoing incident. So you would first go to the application click the button we just created, which take you to the incident form and populates the application name. You would then fill out the remaining fields on that form and save. If there is an update to that newly created incident I would like to have a button on the incident library form that you would click that would take you to a incident update form and populate the application name along with the inputted ticket number on the incident library form.
Hi. If you're talking about something like a "history" or "status updates" to an incident record, you might consider using a form/subform setup. The main form could be based on the incident record and the subform could be based on the "changes."
Hi. If you set up the form/subform properly by using the Linked Master/ Child Fields, then Access should automatically store the foreign keys for you.That is how I have it setup now. What I am looking to do is have the Changes form have fields auto populated like Application Name and Ticket Number so the user does not have to input these into the form every time there is an update.