I'm trying to create a form that allows my audit team to help identify transactions that need further investigation.
Is the following is possible? If so what would be the best method for accomplishing this? I would like to have a check box in a form for each record that is returned from a query. That check box would then be used to identify records that would be appended to another table.
I've done this in the past for forms linked to temporary tables; however, since this form is linked to a query I think I'm having an issue.
You could add the checkbox to the form and use some VBA code to insert all those rows from the query into another table that have the checkbox checked (Forms!MyForm!myCb = True)
Related
I want a user to be able to choose the field they select from a table through the use of a combo box in an MS Access form. My combo box contains a list of all the field names in the table, and when the user selects one I want that field to be queried. Currently, the general syntax of my code looks like this but doesn't return any values when I run it.
SELECT FORMS![formName]!cboName
FROM tblName;
The form is working fine as far as I can tell so I'm pretty sure the issue is with my SQL but I can't figure out where. Any help is appreciated.
I have an access database with several calculated fields in text boxes on a form. Most of those update immediately after the data included in the calculation is updated. However I have a couple of those calculated field text boxes that include a data point from a Query, when I update a filed that would impact the query results, those calculated fields do not update correctly until I click through a few records or close and open the form.
How can I force that specific query to update after updating a specific filed on the form?
Try refreshing the form.
Me.Refresh
As an aside, you really should get out of the habit of using bound forms, because you have to end up kludging a bunch of stuff (like this) to get it to work properly, and the Undo functionality (cancelling the entry of a new record) is unstable at best. By unbinding a form, you can have more control over how it reacts to calculated fields and dumping a new data entry is a snap.
I have a continuous form that has comboboxes down one of the columns. I would like to prevent the same item being selected more than once per order.
The database is basically a microsoft web database template that im trying to modify to suit our requirements (Desktop product inventory database).
My requirement is,if for example a user selects the 350CC shaver shown below, i want the shaver to disappear from the list of available options from then on.
The form is shown below, with the comboboxes down the product column:
The rowsource for the product column is as follows:
The record source for the form itself is as follows:
So, having a very basic knowledge of SQL, i would appreciate some help in crafting the sql statement required to achieve this.
cheers
EDIT - 9-Dec -14
Picture showing orderdetails cleared off the form and error message.
You need to create a unique index using the primary key of the order details table and the product ID foreign key
Then when a duplicate product is selected the system will not allow it to be saved into the table and will throw an error
However this is not available with Microsoft Access 2010 because the backend data is stored in a SharePoint list not directly into SQL Server table unlike Access 2013.
Instead as a workaround you can create a data macro that will essentially do the same thing.
Example of the data macro can be seen in the following screenshot indicated by the red arrow:
http://screencast.com/t/WjU5qws4Ug
When I click the Combobox, the dropdown list is populated, yet when I try to click on an option it says "Recordset is not updateable".. I have tried to read up on this error yet can't identify the issue behind this. The joins aren't complicated and it has worked before. The query source for the AwardsSubFrm is attached:
Anyone know how to fix this?
The image of the query design indicates your record source is a GROUP BY query. The recordset from any GROUP BY query is never updateable. You can verify that point by opening the query in Datasheet View of the query designer and confirm Access won't let you change any of the values.
I don't know what the fix is for your situation, but you need something other than just a GROUP BY query. Perhaps a subform whose record source contains the table rows you want to update, and link it to the main form so it displays those records which are related to the current main form row.
I am creating an InfoPath form and want to retrieve the data from the SQL database. I'm not looking for end users to fill in blank text fields, but rather am just wanting to populate the fields with the data from the SQL Database.
I have searched on some blogs and InfoPath/Microsoft sites to see how this can be accomplished, but many of the things I keep bumping into show how to create fields that the end user can populate instead of fields that are pre-populated.
I have already connected the database that I want to use to InfoPath and 'myfields' are already populated with the table that I am using, so half the battle has been won! :)
How can I accomplish this?
There are a few options available to you...
Firstly, you can look at using rules on the form load or default vlues in your InfoPath forms' fields to populate the fields with data from your SQL (secondary) data source... Take a look at this link here: http://social.technet.microsoft.com/Forums/en/sharepoint2010customization/thread/cb15a237-28cc-4d6b-8225-83181a7497ff
Secondly, you could use managed code on the form load to query the SQL database and then set your returned values to the values held in your fields in your InfoPath form. Take a look here for using managed code to do this: http://vspug.com/ssa/2006/01/03/populating-infopath-fields-with-sql-data-using-managed-code/
I hope this helps...