Ray I eventually solved the issue, not quite sure why but it was an issue with the recordset being used for both the select field and the repeat region. I created a separate recordset for the selection field and it solved the issue.
Unfortunately I'm still having a problem with an update behaviour which uses the select field in the form.
The Update behaviour is triggered by an access rule ( named "multiblock" that is dependent on a URL parameter value ( blocks=2 ). The update behaviour is triggered but the binding used does not seem to work. the binding uses the value from the selection field “block” ( which is chosen by the user ) from the “consent_collation” form . The selection field uses a repeat region to display all the options ( there is currently 2 - ‘Block A’ and ‘Block B’ ). I wonder if its an issue with the options within the repeat region!
Its an issue with the binding in the option selected. Because if I just put in a static number in the “Binding Value” it works.
You can use the same access I gave you in the previous PM.
Ive put database access in this PM if you need it.
Thanks in advance.