C
Chris W via AccessMonster.com
Hi all
I have been grappling with a problem for the last week and have made little
headway, for those who have read my previous posts I apologise for repeating
myself but I think that I have not been explaining myself properly.
What I am looking to do is have a shopping cart feature to my database, to be
implemented after a query and before the user proceeds to a report.
In a previous post I was given a link to a download illustrating the list box
method. However this method essentially is running of a query, which is
already occurring in my database.
In this database there will always be a number of records returned that will
be irrelevant to the user simply by the nature of the data and the subjective
manner in which it is used. The query I have is based on 7 tables and 10
fields in which data can be searched. With that many ways of in-effect
filtering the data the user is unlikely to know all element all the time so
they input (say) 5 and get (say) 20 records and five are irrelevant.
Currently the user other option but to either redefine the search parameters
in the hope of providing a more precise search result, which may actually end
up excluded some desired records or proceed directly to the report including
the irrelevant records. Given that the database report would ideally be
included in a full report to be handed directly to a client the reporting of
irrelevant data begins to undermine the purpose of having a database.
I think in affect what I am looking for is the code for the report to only
report the records that contain a checked check-box on the form in which the
records are displayed. And the code for the checkbox to be cleared after the
form has closed down. I understand that for this to work it is likely that
there would need be a link to the transaction tables primary key so this may
need to included as a field in the table that is left blank or false and then
temporarily made positive/true for the purpose of reporting and then is
removed or made false again.
As I said previously I don’t even know if this is possible, it would seem to
my newbie mind that it is a feature many users would want, so I hope someone
can help.
I hope that explains my conundrum better, and thanks in advance for any
additional guidance anyone may be able to offer.
I have been grappling with a problem for the last week and have made little
headway, for those who have read my previous posts I apologise for repeating
myself but I think that I have not been explaining myself properly.
What I am looking to do is have a shopping cart feature to my database, to be
implemented after a query and before the user proceeds to a report.
In a previous post I was given a link to a download illustrating the list box
method. However this method essentially is running of a query, which is
already occurring in my database.
In this database there will always be a number of records returned that will
be irrelevant to the user simply by the nature of the data and the subjective
manner in which it is used. The query I have is based on 7 tables and 10
fields in which data can be searched. With that many ways of in-effect
filtering the data the user is unlikely to know all element all the time so
they input (say) 5 and get (say) 20 records and five are irrelevant.
Currently the user other option but to either redefine the search parameters
in the hope of providing a more precise search result, which may actually end
up excluded some desired records or proceed directly to the report including
the irrelevant records. Given that the database report would ideally be
included in a full report to be handed directly to a client the reporting of
irrelevant data begins to undermine the purpose of having a database.
I think in affect what I am looking for is the code for the report to only
report the records that contain a checked check-box on the form in which the
records are displayed. And the code for the checkbox to be cleared after the
form has closed down. I understand that for this to work it is likely that
there would need be a link to the transaction tables primary key so this may
need to included as a field in the table that is left blank or false and then
temporarily made positive/true for the purpose of reporting and then is
removed or made false again.
As I said previously I don’t even know if this is possible, it would seem to
my newbie mind that it is a feature many users would want, so I hope someone
can help.
I hope that explains my conundrum better, and thanks in advance for any
additional guidance anyone may be able to offer.