Wrox Programmer Forums
Go Back   Wrox Programmer Forums > SQL Server > SQL Server 2000 > SQL Server 2000
SQL Server 2000 General discussion of Microsoft SQL Server -- for topics that don't fit in one of the more specific SQL Server forums. version 2000 only. There's a new forum for SQL Server 2005.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the SQL Server 2000 section of the Wrox Programmer to Programmer discussions. This is a community of software programmers and website developers including Wrox book authors and readers. New member registration was closed in 2019. New posts were shut off and the site was archived into this static format as of October 1, 2020. If you require technical support for a Wrox book please contact http://hub.wiley.com
Old June 11th, 2004, 11:37 AM
Authorized User
Join Date: Apr 2004
Posts: 12
Thanks: 0
Thanked 0 Times in 0 Posts
Default 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.

Old June 13th, 2004, 10:12 AM
Friend of Wrox
Join Date: Nov 2003
Posts: 141
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via MSN to acdsky


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.

Old June 13th, 2004, 06:26 PM
Friend of Wrox
Join Date: Nov 2003
Posts: 625
Thanks: 0
Thanked 0 Times in 0 Posts
Send a message via MSN to jemacc

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.

Old June 17th, 2004, 08:50 PM
sal sal is offline
Friend of Wrox
Join Date: Oct 2003
Posts: 702
Thanks: 0
Thanked 0 Times in 0 Posts

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.


Similar Threads
Thread Thread Starter Forum Replies Last Post
Access to SQL Server 2000 jgferguson Access 3 December 1st, 2006 12:52 PM
SQL 2000 SERVER+ACCESS ADP DLOOKUP MHONG Access ASP 1 October 25th, 2005 08:36 AM
Access 2000 "Connect to SQL Server" cjdphlx Access VBA 1 July 17th, 2005 02:09 AM
looking for access 2000 to sql server 2000 sql/que method SQL Server 2000 0 July 7th, 2005 12:46 PM
Migrate Access XP to SQL Server 2000 Walden Access 1 September 21st, 2003 01:54 AM

Powered by vBulletin®
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.
Copyright (c) 2020 John Wiley & Sons, Inc.