Combo box in datasheet view

[scheeps]

I've got a parent child form with the parent fields as in tabular format and the child records in datasheet format and I need to add front end data validation to a child field in the datasheet view.

In design view, I've right clicked the field, Change To and selected Combo box for the field I would like to add data validation.

But as soon as I select the Form View, (I have not even specify a query for the combo box) that specific field would disappear from the child datasheet view.

Has anyone else experience something similar? It is probably something simple, but I can't seem to spot it.

Thanks in advance!

 

[vbaInet]

I don't completely understand your dilemma but I suspect the control (not field) is still there and it may well be at the very end. So scroll to the very far right and have a look there. Also check to see whether that control is collapsed.

 

[missinglinq]

Under these conditions you won't see the dropdown arrow of a combobox until you click into the box, but the control should be there, it'll just look like a textbox.

I don't understand what a combobox has to do with 'front end data validation.'

Linq ;0)>

 

[scheeps]

I suspect the control (not field) is still there and it may well be at the very end. So scroll to the very far right and have a look there.

Thanks vbaInet, that was indeed the problem and dilemma

Is there any explanation for why the control is now placed at the end of the datasheet?
And is there a way to control the display order of the fields and controls in a datasheet view?

I don't understand what a combobox has to do with 'front end data validation.'

Instead of the user looking up id's in the parent table and making data entry mistakes, the combo box will contain the id's from the parent table driven by a query. Maybe it is not true 100% front end data validation but to some extent it is some sort of validation.

Apologies for my cryptic questions, but my MS Access skills are not what they are suppose to be; I was given this project and it is a bit out of my comfort zone

 

[scheeps]

And is there a way to control the display order of the fields and controls in a datasheet view?

To answer my own question, I found the "You Can Do That with Datasheets?" URL explaining some not-so-fimiliar datasheet properties.

 

[missinglinq]

Instead of the user looking up id's in the parent table and making data entry mistakes, the combo box will contain the id's from the parent table driven by a query. Maybe it is not true 100% front end data validation

No, it's not validation at all! But it is a well recognized way of insuring that correct formatting and/or data is used in data entry.

And don't worry, each language has it own language, and it takes some getting used to for everyone! And Access doesn't always make it easy! The vast majority of English-speaking people would assume that a 'form' was something that is printed and can be held in your hands! But not in Access-Speak!

BTW, another common way of performing an end-run around some of the limitations of Datasheet View Forms, such as adding command buttons, etc, is to use a Continuous View Forms and tweak them to look like Datasheets.

Good luck with your project!

Linq ;0)>

 

[vbaInet]

Glad to see you've found your "missing" control

Is there any explanation for why the control is now placed at the end of the datasheet?

The order of each field on a datasheet is saved so unless you added a new control to the form, I don't see why it would change order.

And is there a way to control the display order of the fields and controls in a datasheet view?

Open the form in Datasheet View, click and hold the name of the field (i.e. as if you were highlighting that whole column), then drag and drop it in the position you like. Save your form so it remembers the order.