Unfortunately, there doesn't appear to be a way to get Access to require the
corresponding data elements. InfoPath does not import the Access data
fields' "required" states into the corresponding elements (under dataFields)
in the data source. What's worse, the data elements, once created, do not
let you set the "Cannot be blank" checkboxes in their Properties dialogs.
Neither can you change the similar checkboxes in the controls' Properties
dialogs. (you can't create an "unbound" control when the main data source
comes from Access)
Of course, because the fields are set to "required" in Access, there's a
safeguard against actually submitting missing data into the database. But
the form doesn't give you the visual feedback for a required field. The user
only finds out that a field is missing when he or she tries to submit, and
the error messagre comes from the Microsoft Jet engine and isn't particularly
user-friendly.
--
Greg Collins
Microsoft MVP
Visit Braintrove at http://www.braintrove.com
Visit InfoPathDev at http://www.infopathdev.com
Yet there's that "field cannot be blank" checkbox sitting out there
uselessly.
Is there a reason for it?
Is this a known issue?
Frederik Van Lierde
http://BlueInfoPath.wordpress.com ¦ http://www.SilverSandsAssociates.com
¦ Do yuo follow us already? http://twitter.com/frederik_vl