I have a web page that looks like this:
the services are stored in a database table with its associated functions... so for each service there is a set of functions associated with it like this:
the database table snapshot shows the set of functions associated with the BatchItemService only, but all other services have their own functions...
what I want to do is to set the function multiple select as invisible and set it to visible after selecting the service name from the services combobox, in addition, I want the function combobox be populated with the function names associated with the service name selected only.. there is also one more thing, the user can select multiple services.. I'm using jsp with mysql database.
HELP please, thank you!
Related
I am Building an AppMaker App. I have a ChainStores Data model which
has a One to Many relation with a Locations Data Model
I have one page with a list of ChainStores and another page with a list of Locations which should be based on the ChainStore selected.
I would like to have my second page Location to show the data based on what
is clicked on the first page ChainStores.
Thanks!!
You can try this documentation, it said that:
When you create a model, a query datasource is automatically created
with the same name as the model. Whenever, you change the model name,
any query datasource with the same name will also have its name
changed to match the new model name. You can create additional query
datasources for a model. In the model editor, click Add >
Datasource. A new datasource is created with a default name. Often
you will create additional query datasources because you want to have
different options selected for a single model such as having different
sort orders or different page sizes.
To edit an existing query datasource, open the model editor for the
data source. Then expand the Datasources tree item and select the
datasource.
You can also try to this tutorial.
This tutorial teaches you how to:
Create a data model and add fields to it. You learn data-related concepts—data models, fields, records, datasources, and data bindings.
Add form and table widgets to a page. You learn how to modify these widgets and how they work. You also learn the difference between
insert forms and edit forms.
I'm trying to find a way to pass a parameter from a report to a subreport without resorting to any SQL code or macros (my officemates are non-technical, but still have to use the Access database to run reports, occasionally making tweaks to them.)
I'm working in Microsoft Access 2013. I have a table that contains a list of investments as well as which state those investments are based in. I have a query that pulls data on Investments based on a user-entered State parameter. I then run two reports: one that simply lists the investments grouped on different categories, then a second report that summarizes the investment categories into a table. I've put the summary report at the top of the detailed report as a subreport, but I want to pass the State parameter through from the main report to the subreport so the user doesn't have to enter it twice. Is that possible without resorting to writing any SQL code or macros?
Thanks!
I think I understand what you're trying to do, but please add details if my answer doesn't make sense.
You can pass user entered information by referencing by
[DatabaseObjectType]![ObjectName]![FieldName].
If the user is entering the State value from a Form, you'd reference:
[Forms]![FormName]![State]
where FormName is the name of your form, and State is actually the name of the Form control containing the State value.
If the user is entering the State value in a prompt from a query, you'd reference:
[Queries]![Query1]![State]
where Query1 is the name of your initial query that gets the state info from the user, and 'State' is the name of that field.
You put these references in to your secondary query or report:
for example, in a second query, you can set the State field Criteria (in query design view) to be = [Queries]![Query1]![State]
so the second query will pull the State value from the first query
on a report, similar idea - you can set the Control Source of the State control (in Properties) to be = [Queries]![Query1]![State]
I have tried several different ways of searching for this information with no luck so far...
Firstly, I am using Access 2013, and I wouldn't exactly call myself experienced with it...
I have a table with many fields and I want to be able to create a report dynamically that only uses a subset of those fields. The subset is to be determined by a ListBox (with multi select turned on) containing the list of all of the fields.
So, a user will:
Opens the filtering form that was created
Selects the fields they wish to view
Clicks "Generate Report"
The report will only shown the fields that were asked for
Is this possible? If so, how?
I'm working with this table and want to offer the user a Lookup list in one column. I can do this easy if I want to use a whole table.
But I want to show in this lookup just a subset of data.
Like this: SELECT ID, Name FROM Items WHERE Type = 'SomeType'
I have a query, but when I go into Lookup Wizard, I cannot select Queries. Why is this?
This is Sharepoint 2010, editing the Web Database in Access.
If you build a continues form then you would simply drop in a combo box control for one of the columns and then you can build your SQL as you have using the query builder.
For most access applications it really never was very practical to allow users to open and edit data by using tables directly anyway.
And for published web applications you not even allowed to do as such on the web side (so you can edit tables client side, but not web side in a browser).
Using a continues form here should work just fine. So drop in a combo box, build your query as you have. Set number of columns to 2 and bind this combo box to whatever the underlying column is that this first ID value is to be saved to, and you off to the races.
I am new to Access and i am in the process of creating a database for some of our users. I have designed a form where the user name, first and last name etc are inputted.
Some of these users work for more than one department which means I need some type of listbox control that allows them to select more than one department when they enter their contact info.
In VB Studios 2005, this control is called a CHECKED LISTBOX. I have looked everywhere in access but cant seem to find it or anything closely similar.
The option of a listbox or combobox is not feasible here as these only allow the user to select one option only when inputting their details. Any help with this is much appreciated.
Use an ordinary list box with the "Multi Select" property set to "Simple".
The user can then click multiple list items, all of which stay selected until they un-select them again.
You may wish to consider a subform, as this will save you the trouble of updating a table with the data from a list box. A subform can use a department-person junction table with person id as the linked child field and master field. A combobox bound to department id will allow the user to select departments.
If you are really set on having checkboxes, Stephen Lebans has a sample database that uses the built-in Access listbox with checkboxes (from one of the Access wizards).
There is another choice:
If you are using Access 2007, you can declare your field as a lookup field accepting multiple values.
When you bind the list box to that field, you will get checkboxes.
It's easy to use them.
You'll also find more information is available from the MS Office website.
However, note:
This is only possible in the new Access 2007 database format and you will not be able to save your database to the older MDB format.
Multiple value fields are not compatible with most other databases, meaning that if you decide one day to upsize to SQL Server, you'll have to redesign your tables to use a junction table as Remou mentioned.
These multi-value fields are difficult to use from VBA: the value they return is in fact another recordset that you must iterate through to get all the values.
Having said that, if you just want something simple and you're not planning on manipulating the database from code, then it can be a practical option, albeit not a very compatible or future-proof one.
I'm not using them, but I think others should be able make their own decision knowing what is available to them.