I'm trying to deploy a database using developer extensions for users without
the Access app. Help tells me that I can't deploy certain built-in features:
Filter by Form is one of them. Is there an alternative method using macros
that I can embed in my distributed application?

On Sun, 25 Jan 2009 12:21:01 -0800, Maniceye wrote:

> I'm trying to deploy a database using developer extensions for users
> without the Access app. Help tells me that I can't deploy certain
> built-in features: Filter by Form is one of them. Is there an
> alternative method using macros that I can embed in my distributed
> application?

You have to create your own form. It can mimic Filter-By-Form visually
if you wish. This is often referred to as Query-By-Form. You create
queries that use your custom form to get their criteria from.

--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Here are some examples of Query By Form (QBF), mentioned by Rick Brandt in
his reply:

http://www.accessmvp.com/TWickerath/...mdialogbox.zip
http://www.accessmvp.com/TWickerath/...s/elements.zip
http://www.accessmvp.com/TWickerath/.../Chap08QBF.zip

http://www.seattleaccess.org/downloads.htm
See the download "Query By Form"
Tom Wickerath, February 12, 2008


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/ex...tributors.html
__________________________________________

"Maniceye" wrote:

> I'm trying to deploy a database using developer extensions for users without
> the Access app. Help tells me that I can't deploy certain built-in features:
> Filter by Form is one of them. Is there an alternative method using macros
> that I can embed in my distributed application?

Thanks folks . A further question:

Your reply was helpful, but it doesn't quite get me all the way there.
Unfortunately, the example you posted back to me uses stored procedures in a
SQL back-end database. I'm not using this structure. Instead, I have an
Access 2007 front end and an Access 2207 back end. I compile the front end
for distribution on non-access users desktops. How do I implement your advice
in this case?

Many thanks


Derek


"Tom Wickerath" wrote:

> Here are some examples of Query By Form (QBF), mentioned by Rick Brandt in
> his reply:
>
> http://www.accessmvp.com/TWickerath/...mdialogbox.zip
> http://www.accessmvp.com/TWickerath/...s/elements.zip
> http://www.accessmvp.com/TWickerath/.../Chap08QBF.zip
>
> http://www.seattleaccess.org/downloads.htm
> See the download "Query By Form"
> Tom Wickerath, February 12, 2008
>
>
> Tom Wickerath
> Microsoft Access MVP
> http://www.accessmvp.com/TWickerath/
> http://www.access.qbuilt.com/html/ex...tributors.html
> __________________________________________
>
> "Maniceye" wrote:
>
> > I'm trying to deploy a database using developer extensions for users without
> > the Access app. Help tells me that I can't deploy certain built-in features:
> > Filter by Form is one of them. Is there an alternative method using macros
> > that I can embed in my distributed application?

Hi Derek,

> Unfortunately, the example you posted back to me uses stored procedures in a
> SQL back-end database. I'm not using this structure.

And neither am I....I'm not sure what gave you the impression that my
samples are using SPROCs (Stored Procedures). All of the examples I posted
are written for JET databases in the .mdb file format. I haven't attempted to
convert any of them to the newer .accdb file format in Access 2007, as my
primary development efforts involve Access 2003. However, I see no reason
that the samples would not work in Access 2007, either in the .mdb or .accdb
file formats. Of course, with Access 2007, you will need to "trust" the
application (better to simply trust the folder that the file is in) so that
the VBA code will not be disabled.

> I compile the front end for distribution on non-access users desktops.

I just tested one of the samples in runtime mode, and it seems to work fine
in Access 2003. To do this, click on Start | Run, and enter the following:

msaccess /runtime "FullPathToYourFile.mde"
or
msaccess /runtime "FullPathToYourFile.accdr" <---I think that's the correct
extension.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/ex...tributors.html
__________________________________________

"Maniceye" wrote:

> Thanks folks . A further question:
>
> Your reply was helpful, but it doesn't quite get me all the way there.
> Unfortunately, the example you posted back to me uses stored procedures in a
> SQL back-end database. I'm not using this structure. Instead, I have an
> Access 2007 front end and an Access 2207 back end. I compile the front end
> for distribution on non-access users desktops. How do I implement your advice
> in this case?
>
> Many thanks
>
>
> Derek

Hi Tom,

Thanks for your help. You're absolutely right! - the code does work (I guess
fatigue must be kicking in

A further question, if you don't mind:

I've got as far as creating a query form,which runs the query on a button
click, and getting the results to display in a table. I now need to get those
results into a 'results' form. How do I do that?

Thanks again.


Derek


"Tom Wickerath" wrote:

> Hi Derek,
>
> > Unfortunately, the example you posted back to me uses stored procedures in a
> > SQL back-end database. I'm not using this structure.
>
> And neither am I....I'm not sure what gave you the impression that my
> samples are using SPROCs (Stored Procedures). All of the examples I posted
> are written for JET databases in the .mdb file format. I haven't attempted to
> convert any of them to the newer .accdb file format in Access 2007, as my
> primary development efforts involve Access 2003. However, I see no reason
> that the samples would not work in Access 2007, either in the .mdb or .accdb
> file formats. Of course, with Access 2007, you will need to "trust" the
> application (better to simply trust the folder that the file is in) so that
> the VBA code will not be disabled.
>
> > I compile the front end for distribution on non-access users desktops.
>
> I just tested one of the samples in runtime mode, and it seems to work fine
> in Access 2003. To do this, click on Start | Run, and enter the following:
>
> msaccess /runtime "FullPathToYourFile.mde"
> or
> msaccess /runtime "FullPathToYourFile.accdr" <---I think that's the correct
> extension.
>
>
> Tom Wickerath
> Microsoft Access MVP
> http://www.accessmvp.com/TWickerath/
> http://www.access.qbuilt.com/html/ex...tributors.html
> __________________________________________
>
> "Maniceye" wrote:
>
> > Thanks folks . A further question:
> >
> > Your reply was helpful, but it doesn't quite get me all the way there.
> > Unfortunately, the example you posted back to me uses stored procedures in a
> > SQL back-end database. I'm not using this structure. Instead, I have an
> > Access 2007 front end and an Access 2207 back end. I compile the front end
> > for distribution on non-access users desktops. How do I implement your advice
> > in this case?
> >
> > Many thanks
> >
> >
> > Derek

Hi Derek,

> I've got as far as creating a query form,which runs the query on a button
> click, and getting the results to display in a table.

Is this using the method shown in the CustomDialogBox.zip sample?

> I now need to get those results into a 'results' form. How do I do that?

Three of the samples I have available (Elements.zip, Chap08QBF.zip and the
one available on the Seattle Access web site) all use the same idea of an
unbound main form (ie. no recordsource for the main form) with a bound
subform for displaying the results. Of these three samples, the Elements
sample simply displays the results, but doesn't allow one to open a form to
that record. This was done to keep that example as simple as possible--it
simply demonstrates the code required to "iterate" the .ItemsSelected
property of a multi-select list box. (The other option would be to have a
combo box, or set the Multi Select property of list box to None, so that only
single selections could be made, in which case you would use the control
source property--there is no .ItemsSelected property for a single select list
box).

The Chap08.QBF sample, and the sample available on the Seattle Access web
site, allow one to double-click on a record in the subform, to open that
record for editing. These samples require considerably more VBA coding versus
the CustomDialog sample, but I think I was pretty liberal in commenting the
code, so hopefully it won't be too difficult to follow. There is a Word
document that goes with the sample available on the Seattle Access web site,
which is an attempt by me to explain how this technique works.


Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
http://www.access.qbuilt.com/html/ex...tributors.html
__________________________________________

"Maniceye" wrote:

> Hi Tom,
>
> Thanks for your help. You're absolutely right! - the code does work (I guess
> fatigue must be kicking in
>
> A further question, if you don't mind:
>
> I've got as far as creating a query form,which runs the query on a button
> click, and getting the results to display in a table. I now need to get those
> results into a 'results' form. How do I do that?
>
> Thanks again.
>
>
> Derek

Dear Tom,

Thanks very much. I'll give them a try
Derek


"Tom Wickerath" wrote:

> Hi Derek,
>
> > I've got as far as creating a query form,which runs the query on a button
> > click, and getting the results to display in a table.
>
> Is this using the method shown in the CustomDialogBox.zip sample?
>
> > I now need to get those results into a 'results' form. How do I do that?
>
> Three of the samples I have available (Elements.zip, Chap08QBF.zip and the
> one available on the Seattle Access web site) all use the same idea of an
> unbound main form (ie. no recordsource for the main form) with a bound
> subform for displaying the results. Of these three samples, the Elements
> sample simply displays the results, but doesn't allow one to open a form to
> that record. This was done to keep that example as simple as possible--it
> simply demonstrates the code required to "iterate" the .ItemsSelected
> property of a multi-select list box. (The other option would be to have a
> combo box, or set the Multi Select property of list box to None, so that only
> single selections could be made, in which case you would use the control
> source property--there is no .ItemsSelected property for a single select list
> box).
>
> The Chap08.QBF sample, and the sample available on the Seattle Access web
> site, allow one to double-click on a record in the subform, to open that
> record for editing. These samples require considerably more VBA coding versus
> the CustomDialog sample, but I think I was pretty liberal in commenting the
> code, so hopefully it won't be too difficult to follow. There is a Word
> document that goes with the sample available on the Seattle Access web site,
> which is an attempt by me to explain how this technique works.
>
>
> Tom Wickerath
> Microsoft Access MVP
> http://www.accessmvp.com/TWickerath/
> http://www.access.qbuilt.com/html/ex...tributors.html
> __________________________________________
>
> "Maniceye" wrote:
>
> > Hi Tom,
> >
> > Thanks for your help. You're absolutely right! - the code does work (I guess
> > fatigue must be kicking in
> >
> > A further question, if you don't mind:
> >
> > I've got as far as creating a query form,which runs the query on a button
> > click, and getting the results to display in a table. I now need to get those
> > results into a 'results' form. How do I do that?
> >
> > Thanks again.
> >
> >
> > Derek