Unbound/Bound Forms

I have inherited a database that is used to track product development. It is set-up so that one product has one key(product_id). The bosses have asked to be able to track the changes to the product over the development life cycle. I have created a table with the following fields: product_id, change_id, change_notes, and change_status. I have created a form that holds all of these fields, and two unbound boxes. One of the boxes contains an expression that is fed by the product_id from the open form, and the other (to create a change_id) is created by adding a "C" and a now() after the product_id (product_id & "c" & now()).
Problem: I am having an issue getting the unbound boxes to populate the product_id and change_id field in the actual table when I try and save. I am really at a loss. Have been googling calculated fields and before update for the last couple of hours...

Sponsored Links:

Related Topics

Why unbound from as Splash Screen??
Can someone explain why this is? Is it just preference to not have bound forms? Can you not have a splash screen that is bound to anything?

Haven't looked into this too much as I'm pretty novice to the development side of forms and such. Someone mentioned unbound in one of my questions and I just saw a tutorial about creating splash screen and it mentions you should create an unbound form

Why using unbound forms are a bad idea
Unbound forms are forms with no data source, whereas bound forms have one and it’s the default way to bind your form to your tables or queries. Having a data source is the normal way you create Access forms, but it can cause problems no matter how careful you can be:

Datepicker not appearing on Bound Control
I have two versions of the same form, and one for viewing it once it's created.

Both forms have a textbox called Date, which are identical except for one is Unbound and one is bound to the Date field from a table.

The Datepicker only appears on the Unbound textbox - if I unbind the textbox on the viewing form, it reappears.

Why is this? Is there any way of getting a datepicker to appear on a bound text box, or would I have to use a custom calendar control?

Datepicker not appearing on Bound Control
I have two versions of the same form, one for creating a new record, and one for viewing it once it's created.

Both forms have a textbox called Date, which are identical except for one is Unbound and one is bound to the Date field from a table.

The Datepicker only appears on the Unbound textbox - if I unbind the textbox on the viewing form, it reappears.

Why is this? Is there any way of getting a datepicker to appear on a bound text box, or would I have to use a custom calendar control

Why does my Undo button become active for some changes but not others.
I have an Undo button on my form that is supposed to become active whenever a change is made. This works fine whenever I change a bound field.

However, I also have unbound fields on the form. Once I change an unbound field, this appears to mess up the UnDo logic as from that point, changing a bound field no longer causes the Undo button to become active.

Ideally, I'd like the UnDo button to work with both bound and unbound fields but at least I'd like to prevent the unbound fields from messing up the UnDo for the bound fields.

What is a unbound form in Microsoft Access?
Basically it is a form that is not bound to any database table or query. You can usually determine if a form (or a control on a form) is bound by looking at its record source property which will either be bound to a Table, Query or SQL String. Also if you look at each control on the form you will find that each control has a Control Source, which is derived from the field names made available in the Record Source. A bound form is easier to create and requires minimal programming (if any). It allows for rapid application development since Microsoft Access is designed to make application development fast and easy. An unbound form on the other hand requires a lot of programming, BUT gives you near total control over how your application is going to work. This in some cases outweighs the numerous benefits offered by bound forms.

AfterUpdate issue
In my form I am trying to change a bound field with the value of an unbound field that occurs before it on the form so this new value shows up in the table for that field. The unbound field contains a number from a field on the previous record from the table, and the next field, the bound field, is to get that value. I used the AfterUpdate event in the unbound field property, where unbound field = the bound field. I tried this with the control property, then tried using the AfterUpdate event for the form, and no value appears in the bound field and doesn't show up in the table. Both these fields are in a subform. I used the "Me." prefix for both fields and that doesn't work. Probably some minor thing I am not seeing

Force SQL update on a bound form
I am trying to force a bound form to execute an SQL update (and a few housekeeping tasks) before I navigate to the next record, even if I am only updating an unbound control (listbox). The beforeUpdate event only seems to fire if I change one of the bound controls on the form. I have to have both bound and unbound controls (I think) because there is a many-to-many relationship between the bound record and the items in the listbox (so I am using a collection table).

If anyone could provide some information on a possible solution, or some better definition on the event order when the form's navigation buttons are clicked, I would be greatful. I am using Access

sum in form footer
I have this problem and I cant figure it out how many times I have tried it myself.

I have this subform, and it has 4 textbox: three that is bound and the one that is unbound form.

when I do calculations in the bound textbox, I can successfully arrive at the sum of textbox3 but when I sum the fourth unbound textbox, it give an error inside the textbox.

Does it mean I cannot make a summation of an UNBOUND textbox

Bound vs. unbound controls
What is the difference between bound and unbound controls in MS Access? How do they differ? And when on an MS Access Form in design view, how can we tell if a form is bound or not?

Updating default value of bound form from an unbound text box
I have a bound form that I am using to add new records. At the top of my form is an unbound text box ([txtInitials]) that the user will type into. I want to take that value and have it be the default value for one of the bound text boxes ([CheckedInBy]).

I have set the default value of [CheckedInBy] to be =[Forms]![Incoming]![txtInitials]. This does the trick for all of my records except the first one on the form since that blank line is uploaded before the user types into [txtInitials].

I have also tried the code below in hopes of refreshing the [CheckedInBy] text box to contain the default value I have designated for it...

Ordinal Number Format
I have a number field on my bound forum. The form is used to only display the records. I don't use the form for entering new record. I do that running an Update querry from an unbound form. What I need on the number field is to show the number in ordinal format (1st, 2nd, 3rd, 12th, etc.). I need to do this on the unbound form as well, so that when I enter the number, it should show the number in ordinal format. And then the bound field on the bound form should also show this number in ordinal format. When I print reports, I need this field to be in ordinal format. I have to keep this field in Number data type because it is used in calculations within queries and forms

Spacing of Fields on Access2007 forms
When creating forms using Access2007, if I draw fields from a query, table, etc. such that it is a bound field, I find it difficult to insert an unbound field between them in the design view.

Played with padding in Properties. Is there a property that keeps those fields together? Looking for a way of "undoing" formatting, inserting new fields, shifting the fields around, and then reinstating WITH the newly inserted unbound field.

subforms in unbound forms
I have unbound forms name: Project_List, in it there is two subforms bound in a query. Is there a way to link the two subforms, so that when I click a record on the first subforms. it filters a related records.

Let's say in field name: Doc_Name when I click a record from this field, access will filter related date in the 2nd subforms.

Multi-value Unbound Combo Box
I've read a few posts that state it is not possible to have an unbound multi-value combo box (Access 2007). Many of my bound forms have multi-value combo boxes, and I understand many programmers dislike them as they break some formatting standard rules (or so I've read). Anyway, I have no opposition to them since they work fine for the applications in which I've used them. Is it truth, myth, legend that they cannot be unbound? Is there a way to hardheadedly code this possibility into existence?

Let's see where this gets us

unbound text box filter by form on Split Form
I have a split form, with several unbound text boxes, which I would normally use as a filter by form type function. the query has criteria bound to these text boxes.

My problem is that I cannot seem to get the mouse to focus on the unbound text boxes on this split form. when I click in the unbound filter by form text box, the focus immediately moves to the first text box that is bound to data on the form.

Then I will try recreating my split form in a different way. if it is a problem, If perhaps a split form cannot have any unbound data entry controls on it, then I could create a form with the search criteria on, and keep the forms separate. If I was to do this, though I would like to 'dock' this form at the top of the window, and then have the split form 'dock' underneath, as if there was an application level window splitter control. Another option might be to put the filter by form text boxes in the ribbon, and I have added some stuff here, but I am unsure how I might refer to the control in a query criteria.

How do I change txtbox from bound to unbound
Can anyone tell me how you change the 'bound' property of a textbox to 'unbound' or the other way around. Or how do you specify it when adding the box?

Call/pass Value from SubForm to MainForm
I would like to insert the value from a bound control on a subform to an UNbound control on a main/Parent form.

e.g., insert value in subform.pos_sts into an UNbound control on MainForm.

Of course the value in the subform control changes as you scroll through records so the value in the UNbound Control on Main/Parent form should change accordingly. I have tried something like =[forms]![SubformNm]![ControlName] in the UNbound control on the Main Form .but was getting #Name error?

Export to Excel from unbound subform datasheet?
I have an Access 2003 adp project. In it I have a search form/subform. The form provides controls for the user to select search criteria, the subform is a datasheet that displays the search results. I have designed this as an unbound subform, I set it's recordset property in VBA code.

However, I am finding that I cannot export this datasheet to excel, nor can I print it. These functions only seem to work for bound forms. My subform datasheet has the columns ordered in a certain way (across the top) and some columns are hidden so I would really like to be able to export it (DoCmd.OutputTo) rather than copy trhe underlying recordset to excel which outputs all fields in wronmg order etc.

So is there a way to export and print unbound forms / datasheets?

On Trapping Refresh Key and Escape Key.
I have bound forms over my database and it's causing some significant unwanted updates every now and then; even when users does not intend to.

I have discovered that the two main culprits so far are the:

1. Escape key (when it can't detect dirty event.)
2. Refresh key (when user press it, whatever is in the form whether it's filled out or not, it will be updated automatically which is a major pain.)

I have already trapped my Escape Key and as of now, I intend to trap Refresh key also.

A. Do trapping both of that keys on selected forms would somehow backfire on the integrity,function and overall stability of my database in the long run?

B. Is there any other way to secure entry and tighten up control over update and saving process while preventing accidental unwanted updates?

I can smell unbound forms, but I want answers for bound forms only if possible.