Controls

Re: Can you add a unbound control to a database form?

moggy — Thu, 23 Jul 2009 20:23:18 GMT

Ah now that is better thanks

Re: Can you add a unbound control to a database form?

Hilary Stoupa — Thu, 23 Jul 2009 15:51:46 GMT

You can also add fields to your main data source in a database bound form -- you have to add them at the root node, however. If you right-click the root node (probably myFields), you should see the Add option enabled. You can add as many fields or groups as you need.

Re: Can you add a unbound control to a database form?

Jimmy — Thu, 23 Jul 2009 01:03:57 GMT

A dropdown control is useless if it is not bound to a field. If there is not a field to store the control's value, the control can have no value.

But what you can do if you really don't want to store the value in the form's main data source is to create a simple "Form Logic" secondary data source from an .XML file. It can be something like this:

<?xml version="1.0">
<formLogic>

<dropdownValue>widgets</dropdownValue>
</formLogic>

One consequence of this, though, is that the value of the dropdown will not persist if you close and re-open the form.

Can you add a unbound control to a database form?

moggy — Thu, 23 Jul 2009 00:04:13 GMT

I want to add dropdown list containing Yes/No I do not want to bind it to a database as i don't need to save the value. I want to ues the value to determine what controls are enabled and what part of a workflow is triggered.

However whatever control (tired check box, option button etc) requires you to bind it to a field.