I have a single combo box which selects data from a table called Roster. It chooses all Scout_ID's and Full_names and displays them so the user can choose a record to enter data against.
I am not sure how much detail you would like, but the basic problem is that the combo box populates the key field (Scout_ID) but fails to populate the Full_name field on the same form.
The interesting thing is that different form uses the same technique, however, it populates both ID and Name perfectly. I have been working with Microsoft support for a week and they can't explain it either.
Can anyone help?
Related
I'm struggling with a problem which I can't work out is due to a logical error, a design error or both. Or maybe it's something else entirely.
I have created a simple customer services database and form based user-interface for my company. When a user answers the phone they are supposed to log the call in the system if it is an issue relating to a product.
Sometimes a chain of stores which we have a special relationship with calls up on behalf of customers and we take their reference number and give them ours. This system actually works pretty well if I may say so myself (!), but I noticed after a while that when this store calls up and gives us their number, when they are logged into the system their branch number/name is not updated in the table record.
Here is a summarised outline of the relevant database tables. I renamed the store to SpecialStore:
Issues
IssueReference
ProductID
CustomerID
SpecialStoreBranch
Customers
...
Products
...
SpecialStore
SS_ID
City
Address
The idea is that even if it is either a customer or the store with their own IDs, the products are still stored in the same Products table, just with either the CustomerID or SS_ID filled in. Then when issues are logged, the store or customer is set and logged against a product.
In my main form I have a variety of boxes for a new issue to be filled in. There are combo boxes to select the CustomerID, ProductID etc, and of course the SpecialStoreBranch. These are all bound to the table, and the combo boxes all have row sources relating to their particular table. E.g. CustomerID combo box is a list of the IDs in the Customers table. (This is filtered to the required one elsewhere in the form.)
The Issues table SpecialStoreBranch field has the following query as its Row Source:
SELECT SpecialStore.[SS_ID], [SpecialStore].[City] FROM SpecialStore;
This is the same row source for the combo box on my main form.
The Column Count is 2, with the Bound Column as 0 and the column widths, if necessary, are 1cm;2.544cm.
My main form combo box SpecialStoreBranch has the other attributes:
Limit to List = yes
Allow Value List Edits = no
Inherit Value List = yes
Show Only Row Source Values = no
On the form the CustomerID and ProductID store correctly when the record is saved, and they are also from combo boxes. The form refreshes to update those fields when another part of the form (adding new customers and products) is changed. Could this be why the SpecialStoreBranch does not update? What am I missing? Is there a way to test this? I have been trying to run user tests to see if it ever works, but all I know is that it doesn't always set. If I have forgotten a piece of information let me know.
Edit:
Looking here: BoundColumn-Propery, I'm not sure if setting the bound column to 0 is doing what I think it's doing. But even then it should still use that id number to input into the table I would have thought and if they are all the same, what does it matter. When I tried setting it to 1, it took the text value in the table. Confusing!
I've created a dropdown box in layout mode of filemaker and specified a field to pull in. However the box is remaining blank and not pulling in any of the information from the field in the table. What can have been missed for this to happen?
Most probably it is the problem with the value list set up or the relationship you are using to pull in the data for your drop-down.
If you are using a value list from a related data, place a portal based on the same relationship on the same layout and see if data comes through. If it does not - resolve your relationship first.
If you are pulling all values from a field in the same table, make sure in the value list setup you select the same relationship as the one the layout based on, the target field is selected and "Include all values" option is checked
I am attempting to set the value of a combo box from a "Splash Screen" type form in Access that will take the user's computer name and load two combo boxes on another form with the Employee ID and Manager ID, which are both bound columns of the combo boxes, which are unbound themselves. I can get the IDs in the combo box, but i want it to still display column 2 (Names) of both combo boxes. Right now it just displays the IDs. Anyone got any ideas how i can get it to react like i actually picked it in the combo box?
So, comboboxes can sometimes be tricky, but once you get it down you should be good to go.
So, when looking at a Combobox's properties,
The Format tab :
ColumnCount: 2 <-- You want the ID and the Name
ColumnWidths: 0";1" <--- You're hiding the ID field, which is the first column
The data tab:
This is where you're going to tell Access what data you're supplying for your combobox.
Usually it's a query or table data source. If it's a query you should be selecting the ID and Name fields, and use that query in the RowSource property in the Data tab.
Row Source: Select ID, Name FROM YourTable
Row Source Type: Table/Query
When you use the Wizard to create the combobox, it's fairly straightforward. When Access asks you to format your data source, you completely shrink the ID column, so it hides it (but it's still there).
The steps would be:
I want the combobox to look up the values in a table or query
Select the Table or Query
Select the Fields (ID and Name seem appropriate for your scenario)
Any sorting you may want
The next screen is where we want to hide our ID column, so shrink it entirely
The next screen is where we tell Access that we want the ID to be in scope (selected) when we select a combobox item
Name it & be proud
I am new to Access and I am using Access 2013. I have a table called Employees which has the employees First_Name, Last_Name and then a Combo Box that is going to have the Full_Name. I have a query that pulls the First_Name and the Last_Name and Concatenates it to the Full_Name field.
Now when I go to my form and add a new employee and click save the field Full_Name in the employee table does not take the Firs_Name and Last_Name and put it into that field. I am not sure what I am missing. I have to go to the Full_Name field after I put the new employee in and go to the drop down where the Full_Name is there. I would like it to automatically put the Full_Name in there.
There are two possibilities that I see:
A. The table is updated, but the form isn't refreshing.
Access forms often don't refresh data as instantly as you would like, and that could be the problem here.
If you add a record, close the form and re-open the form. Does the combo box show correctly?
Try adding a record and clicking "Save". Then press Shift-F9 on your keyboard. Does that make the combo box show correctly?
If yes, then that's the problem. You need to add a requery or refresh method to the VBA code for your "Save" button. (From what you've written, I'm presuming there is VBA code in there.)
B. The table isn't being updated.
If the tests above didn't work, that suggests a field in the table hasn't been updated. You are doing it manually, when you pick the Full_Name in the combo box. In that case, you need to revise the code for the button.
About First and Last Name:
It is better to not have fields for full name, last name and first name -- that means you are storing the names twice, which will lead to problems in your situation.
The typical arrangement is to store first and last names. You can obtain the full name by concatenating those two, which you can do either in a query or in the form.
Alternatively, you could store the full name in one field. To obtain first and last names, you would separate them using functions -- again, in a query or form. This is less common, because less flexible. But it still avoids the problems that are created by storing the same data twice.
Which one is better? That simply depends on your needs.
I have a combo box that I have to select a name from (I already have the access data names loaded in the combo box). After the user selects a name the program should display in three separate text boxes the date of hire the id number and the salary. In addition to that if the employee works full time there is a radio button that should be checked.
I have no idea how to do this. I'm using MS Access.