That sample database is not filtering a result. What it does is use the
first DAP to let the user select the record desired, and then it opens a
second DAP that shows the selected record. This is a scenario that should be
workable for what you describe.
Otherwise, perhaps this MSDN article will be the approach you wish to use:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnacc2k2/html/odc_customfilteringandsearching.asp
--
Ken Snell
<MS ACCESS MVP>
"Rod Makin" <rods_junk[ at ]hotmail.com> wrote in message
news:%23$ZznmO1GHA.2036[ at ]TK2MSFTNGP05.phx.gbl...
[Quoted Text] > Thanks for the help Ken, though this is just filtering the results rather > than selecting a specific record. What Id like to do is have where clause > in the SQL statement that can be populated dynamically from the data > access page. Any ideas? > > > "Ken Snell (MVP)" <kthsneisllis9[ at ]ncoomcastt.renaetl> wrote in message > news:eN4aHmp0GHA.4476[ at ]TK2MSFTNGP05.phx.gbl... >> Here's one way to do this: >> http://www.cadellsoftware.org/SampleDBs.htm#FilterDAP>> >> -- >> >> Ken Snell >> <MS ACCESS MVP> >> >> >> "Rod Makin" <rods_junk[ at ]hotmail.com> wrote in message >> news:enANxBp0GHA.4264[ at ]TK2MSFTNGP05.phx.gbl... >>> Is there a way that I can prevent a data access page from retrieving >>> data until I have made a selection? I want to simply retrieve the row >>> that Im interested in and nothing else. The query that Im basing my DAP >>> brings back lots of data which, ultimately will be slow, so Id rather do >>> it right the first time. >>> >>> Thanks in advance >>> >>> >>> Rod >>> >> >> > >
|