**********
**********
Last edited by SKraljica; 09-11-2020 at 02:58 AM.
Not exactly sure what you want or what you mean. Maybe you need to set the default property for a form control so that when you begin to create a new record, that field has a value that you specify. However, when you begin creating a new record, any value that might be there really isn't yet (it has not been saved/committed) so there really isn't anything to get. So when you say "every new row should to have next record from the table" when you're creating a new record (row) that record does not exist yet, and there certainly is no "next record".
If that doesn't help, then you should provide an example of what you'd like to see at the beginning, what you'd like to do at that point, and what it is you'd like to end up with.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.
**********
Last edited by SKraljica; 09-11-2020 at 03:02 AM.
Based on that, I'm thinking that you join table1 on table2 data fields in a query and base your form on that query. The combo box is bound to the query "data" field. After the last record in your form, the combo will be blank on the new record row. You choose a combo value and input your custom data (those fields are bound to the query fields as appropriate). When you move off of this record, it will be saved as entered, subject to any restrictions imposed by table field properties. I would create this query and see if you can edit/append with it before binding controls or form to it. If you have any restrictions or features that make the query uneditable, then that is an issue that needs to be overcome first. Note that this approach would permit a user to change the value of the combo, and since it is bound, the new chosen value would be in that record, which may not jive with the rest of the record. If that could be an issue, then one way to deal with that is by comparing the OldValue property to the current Text property value. If they are different, you can over-ride or message to confirm the change. The OldValue property can only be used with bound controls.
Another way of dealing with this would be that the continuous form is on a main form and the combo is on the main form and is unbound. However, this requires a bit of a work around: https://www.access-diva.com/f2.html
Others may have better ideas than me and hopefully will chime in.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.