The toolbar "Filter by Selection"....How to make? (1 Viewer)

[Mike375]

The toolbar "Filter by Selection"....How to make?

Does anyone have any ideas how it could be made because it will be for a Runtime Access.

The way it is used on the toolbar is as a filter down and not always on the same fields and usually two or more fields would be involved.

 

[James Dudden]

Hi,
You can still use the filter by selection in Access Runtime. If you don't see it on your toolbar you need to add it. Try the following steps:

1. Open your database in a full version of Access.
2. Open a form in design view.
3. Right-click on the toolbar and select Customise.
4. Click on the Toolbars tab and click New.
5. Choose a name for your toolbar and then you should see a small new toolbar with nothing on it open up.
6. Now you need to add commands to it, so click on the Commands tab and select the categorie you require. Now drag the items you want on to the new toolbar. The filter by selection command is under the Records category.
7. When you have finished creating your toolbar close the Customise window.
8. Now in your form properties on the Other tab under Toolbar you should be able to select your new toolbar. Do this for all your forms and save as you go.

Hope that helps

Regards
JD

 

[Mike375]

Many thanks.

I got that working OK.

It finsihed as a very deep (or high) toolbar, about like the depth of hight of two or three toolbar rows but I could change it so toolbar only listed Add Ins.

I also dragged it to the tool bar in form design (on the same row or level) and it then it also appeared as Add Ins.

Does that sound right?

 

[adi32]

Hi,
You can still use the filter by selection in Access Runtime. If you don't see it on your toolbar you need to add it. Try the following steps:

1. Open your database in a full version of Access.
2. Open a form in design view.
3. Right-click on the toolbar and select Customise.
4. Click on the Toolbars tab and click New.
5. Choose a name for your toolbar and then you should see a small new toolbar with nothing on it open up.
6. Now you need to add commands to it, so click on the Commands tab and select the categorie you require. Now drag the items you want on to the new toolbar. The filter by selection command is under the Records category.
7. When you have finished creating your toolbar close the Customise window.
8. Now in your form properties on the Other tab under Toolbar you should be able to select your new toolbar. Do this for all your forms and save as you go.

Hope that helps

Regards
JD

GREAT !!!!
thank you
but Filter By Form works perfect in MDB but does nothing in MDE
Also i want to know how can i have access to the main windows tables reports etc

 

[James Dudden]

but Filter By Form works perfect in MDB but does nothing in MDE
Also i want to know how can i have access to the main windows tables reports etc

This may be of use to you, it is from the Help file:

If your database contains Visual Basic code, saving your database as an MDE
file compiles all modules, removes all editable source code, and compacts
the destination database. Your Visual Basic code will continue to run, but
it cannot be viewed or edited, and the size of your database will be reduced
due to the removal of the code. Additionally, memory usage is optimized,
which will improve performance.

Saving your database as an MDE file prevents the following actions:
� Viewing, modifying, or creating forms, reports, or modules in Design view.
� Adding, deleting, or changing references to object libraries or databases.
� Changing code using the properties or methods of the Microsoft Access or
VBA Object models � an MDE file contains no source code.
� Changing your database's VBA project name using the Options dialog box.
� Importing or exporting forms, reports, or modules. However, tables,
queries, and macros can be imported from or exported to non-MDE databases.
Any tables, queries, or macros in an MDE database can be imported into
another database, but no forms, reports, or modules can be imported into
another database.

Since it only affects VBA code, there's never any point making your back-end
database (the tables) an MDE. If you want to prevent your users from
changing the code (and gain a very slight performance edge), it probably
makes sense to conver the front-end database to an MDE.

Regards
JD