Stuart McLachlan
stuart at lexacorp.com.pg
Mon Apr 5 20:12:01 CDT 2010
I do it all the time - it is a great combination. It combines the security of SQL Server with ease of use of access reporting. A couple of tips: 1. Whenever possible, create Views in SQL Server that combine tables as required and link to them rather than doing your joins in Access. 2. Use the built in SQL Server security features - Create a user/role with Read-Only access to the data and set up your connections using those credentials. -- Stuart On 5 Apr 2010 at 19:27, Brad Marks wrote: > We have done a little experimenting and things seems to work nicely in > our preliminary tests. Do other firms do this (use Access just for > report writing against SQL-server data). Are we missing a big "gotcha"? > > ~ ~ ~ > Is it possible to force "Read Only" access in the Connection String? We > want to ensure that no one ever updates any of the data in the SQL > Server tables.