Is record filtering in runtime version of Access possible?

[sweeneysmsm]

I split a database and made the install package with the developer
extensions. I do encounter one problem and I just want to know if that is
part of the runtime version of Access. When a user is using the front end
with the runtime version of Access. and a linked back-end, they seem to have
no filtering options. They can't click into a field which displays data they
are looking for , eg, the name of a State, and then right click and choose
filter by selection. There seem to be no filtering options available in the
runtime version of Access. Is this true or is there something I should be
doing in the package preparation that would allow this kind of option.

Any insight greatly appreciated.

Mary

 

[Rick Brandt]

I split a database and made the install package with the developer
extensions. I do encounter one problem and I just want to know if
that is part of the runtime version of Access. When a user is using
the front end with the runtime version of Access. and a linked
back-end, they seem to have no filtering options. They can't click
into a field which displays data they are looking for , eg, the name
of a State, and then right click and choose filter by selection.
There seem to be no filtering options available in the runtime
version of Access. Is this true or is there something I should be
doing in the package preparation that would allow this kind of
option.

Any insight greatly appreciated.

Mary

It is not that filtering is unavailable in the runtime. It is that all
built-in menus are unavailable in the runtime (including right-click menus).
You have to supply custom menus for all such functionality.

 

[sweeneysmsm]

Thanks so much, Rick.

Would I be correct in thinking that creating a macro that would display the
FormView toolbar (or the PrintPreview toolbar for a Report) where appropriate
and run on the OnOpen event of a form would not work?

If the above is true, could I get around it by creating a Custom toolbar and
assign that to a macro? If not, how do I create custom menus?

I ask these 2 questions particularly in trying to determine exactly where
and when I would create these. Should it be done prior to splitting the
database (front end/back end)? Is it done after the split in the front-end so
that these features get included in the package that includes the frontend
and run-time version of Access?

Thanks.

Mary

 

[sweeneysmsm]

I should have added that am working in Access 2003.

Mary

 

[Rick Brandt]

Thanks so much, Rick.

Would I be correct in thinking that creating a macro that would
display the FormView toolbar (or the PrintPreview toolbar for a
Report) where appropriate and run on the OnOpen event of a form would
not work?

Yes, that would not work because those built-in toolbars are not available
in the runtime. If you made custom toolbars with all of the same commands
then you could use those instead.

If the above is true, could I get around it by creating a Custom
toolbar and assign that to a macro? If not, how do I create custom
menus?

I ask these 2 questions particularly in trying to determine exactly
where and when I would create these. Should it be done prior to
splitting the database (front end/back end)? Is it done after the
split in the front-end so that these features get included in the
package that includes the frontend and run-time version of Access?

Built in menus/toolbars (and any modifications you make to them) belong to
Access itself and the the runtime version of Access does not support them.
Custom menus/toolbars belong to the MDB file in which they are created.

Right-click on a toolbar while you have your MDB opened and choose
"customize". In the resulting dialog there is an option for "NEW". It
should be self-explanatory from there.

 

[Ken Sheridan]

Mary:

The built in Filter By Form facility is not supported in the runtime
environment as this is considered to be a 'design view'. I'd imagine that
the same is true for Filter By Selection, but am not 100 per cent sure on
that. Filtering per se is possible, i.e. you can set the Filter and FilterOn
properties of a form, but if you want a Filter By Form facility then you'd
have to design your own unbound form and write code to examine the controls
on the form and either set a bound form's Filter and FilterOn properties on
the basis of the controls' values, or change the RecordSource property of a
bound form to a query which restricts the rows returned and then requery the
form.

Ken Sheridan
Stafford, England