p2p.wrox.com Forums

p2p.wrox.com Forums (http://p2p.wrox.com/index.php)
-   SQL Server 2000 (http://p2p.wrox.com/forumdisplay.php?f=20)
-   -   SQL SERVER 2000 AND ACCESS 2000 (http://p2p.wrox.com/showthread.php?t=14101)

ckentebe June 11th, 2004 11:37 AM

SQL SERVER 2000 AND ACCESS 2000
 
Hi y'all,
Can someone walk me through setting up an Access 2000 App as a front-end and MS Server 2000 as a back-end? The Access App has 15 users and is placed in a shared drive. The users want a log of changes done and by user and date. Do I write a trigger on the tables on the SQL Server or using VBA (which I am NOT experienced) ?
Any help would be appreciated.
Thanks



acdsky June 13th, 2004 10:12 AM

Hi

All you need to do is link the tables to your SQL server. It will probably be a good idea to have a access BE with the linked tables and the FE linking to the access BE. This way you only need the ODBC connection on one central server instead of every client machine. Once you have linked the tables you use the access DB the same way as any access database.

Regards
Marnus

jemacc June 13th, 2004 06:26 PM

As an alternative you can use access project as your front end and SQL as your back end. Develop your application and distribute to all users. Use SQL to handle all your security, constraints an access to to your database objects.


sal June 17th, 2004 08:50 PM

On keeping changes by datte and user, it depends on how comlicated you want your life to be. You can use a default value for a field that sets to getdate() for entered date, a trigger for last update date and a default value of CURRENT_USER() in a field for enterd by, and in the same trigger you can set another field for last changed by. You must use distinct usernames for each individual who will be using the database and it would be best to use windows authentication (read about it in books on line) and use role based security for permission levels.

Or you could use a table that inserts a new record after every change on a table and do all the data adds / edits / deleted by stored procedure and then you can keep true history of how much your users change data for dumb reasons and you will be able to brag about how much you hate life because it will take you a long time to implement :(. Just kidding, if that is what you need, it does take a while and makes your database grow too large.



Sal


All times are GMT -4. The time now is 07:36 AM.

Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.