C
Charles D Clayton Jr
I was recently reading in "Access Cookbook" about storing your queries
as SQL in a table for better security (pp 55-56). The idea is to take
the SQL of your query and put it in a table and then make a function
that will retrieve the SQL and assigning it to your Form's/Report's
RecordSource using the "On Open" Event. Consequently, no one ever
sees your queries except through code because you do not have an saved
queries. Further security would be achieved by storing them in a
library database. Mr Litwin (the author of this chapter) notes some
dangers and that it takes slightly longer to compile the SQL and run
it as opposed to using saved queries but the payoff is that no one
sees your queries.
What do you think about this?
Charles D Clayton Jr
as SQL in a table for better security (pp 55-56). The idea is to take
the SQL of your query and put it in a table and then make a function
that will retrieve the SQL and assigning it to your Form's/Report's
RecordSource using the "On Open" Event. Consequently, no one ever
sees your queries except through code because you do not have an saved
queries. Further security would be achieved by storing them in a
library database. Mr Litwin (the author of this chapter) notes some
dangers and that it takes slightly longer to compile the SQL and run
it as opposed to using saved queries but the payoff is that no one
sees your queries.
What do you think about this?
Charles D Clayton Jr