Securing Access data? SQL 2000 alternative?

[Guest]

I have a client that is pulling data from DB2 tables and bringing them into
msAccess to produce reports. The data is secure at the datasource (DB2
tables). But, once it is brought into msAccess they lose that security. You
can easily make tables or even export the data outside of the secure DB2
enviroment. They may drop the use of msAccess and use Crystal Reports only to
access the DB2 tables.

Is there another alternative?
Could SQL 2000 link to the DB2 tables and then within SQL 2000 somehow
secure access to the table to read only?

No manipulation of the data would be possible except with a select query. No
exporting of data, no make tables... you get the idea.

 

[Rick Brandt]

I have a client that is pulling data from DB2 tables and bringing
them into msAccess to produce reports. The data is secure at the
datasource (DB2 tables). But, once it is brought into msAccess they
lose that security. You can easily make tables or even export the
data outside of the secure DB2 enviroment. They may drop the use of
msAccess and use Crystal Reports only to access the DB2 tables.

Is there another alternative?
Could SQL 2000 link to the DB2 tables and then within SQL 2000 somehow
secure access to the table to read only?

No manipulation of the data would be possible except with a select
query. No exporting of data, no make tables... you get the idea.

Just pull the data from DB2 with a Passthrough query instead of importing it.
Whoever runs the query will have to have permissions on the DB2 table or the
query will fail.