Hiding query definitions 1

[MBorofsky]

I am looking for a way to hide query definitions from the user. We want them to be able to run reports off of these queries but not see the SQL/design view of the query. We also want to prevent them from viewing the reports in design-view. Using user-level security I can prevent the user from modifying queries but that isn't really what we want.

We want to eventually move everything to SQL-server anyway because some of the end users will have millions of records (we already have a backend there but translating the queries will take longer than we have). A solution that involved moving the queries into Microsoft SQL-server first and then encrypting them there would be fine as well.

At this point the only other thing I could think of was writing the query definitions in VB-code and saving the results in tables. It runs quickly enough but the backend would grow quickly, we would have to compact-repair fairly frequently.

 

[PHV]

SELECT DISTINCT SubQ2.fieldX, SubQ2.fieldY FROM [SELECT fieldA FROM tblA]. As SubQ2
How can you select 2 fields from a query returning only one ?

Hope This Helps, PH.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244

 

[LittleSmudge]

Ignoring ( for a moment ) the missing fieldB from tblA in MBorofsky 's example,

The real problem is that Access only copes with one [ .. .. ]. sub clause.
All of the other sub clauses have to be ( .. .. )

I don't know of anywhere that explains it - but from experience :-
If you have ONE sub clause it needs to be [ .. .. ].
If you have more than one sub clause then all the rest must be ( .. .. )
If fact if you have more than one sub clause they can all be ( .. .. ).
So the ONLY ONE subclause becomes a special case.


G.


G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.