Hi,
Yes wrong data is stored if I go too quick.
I give an example of the code for the most complicated field: breed (ras in dutch)
In dutch coding ; is used in stead of ,
On a datacard of the breed (ras) field of table animals (dieren) I remove the text input control.
I instead put a dropdown.
I set the items property of the dropdown to
Filter('[dbo].[ras]';diersoort_id=Value(Label3.Text))
(I do this so only the breeds are shown that are compatible with the species (diersoort))
I set the default value of the dropdown to
LookUp('[dbo].[ras]';ras_id=Parent.Default;naam)
The value property is naam, the name of the breed (did not set this myself i think, went automatic)
Label 3 is an invisible label I use to temporarily store the diersoort_id from the animal table
The default value for the datacard is just: ThisItem.ras_id
I have 4 dropdowns on the edit form
-breed (ras) see above
-species (diersoort)
-color (kleur)
-furtype (vachttype)
In the last 3 the dropdown is not filtered, they just use a master table.
They do use sorting for example the items property of the species (diersoort) dropdown
SortByColumns('[dbo].[diersoort]';"naam";Ascending)
Like I said: all function perfectly if you give them time.
If I would use a timer to solve this would it not just make the error less probable in stead of impossible?
Like: If the connection is bad my rabbit gets turned into a dog?
