Access and Sql server

xcao

Registered User.
Local time
Today, 09:31
Joined
Nov 25, 2003
Messages
40
I created a webform using asp.net2.
It collects data in sql server 2005.

Then I need to create some reports upon the data. At first, I think I can use sql server reporting services. But this way she can only pull read only reports.
I think maybe later our staff may need to change some data or even enter some records into it, maybe I shoudl create an Access database(we use office 2003) so that she has better control, and she can also change or enter data. Then I can create Access database instead of Sql server reporting.

1. Is this the right way to go?

2. By creating the database, shall I create one and link table using ODBC, or shall I create a project to connect to sql server?

3. if the staff working on the access database, I think it's considered as one user connecting to the sql server, will that sometimes lock the database or not, I don't want when it affects front end web users wehn she working at the access database?

Thank you in adcance
 
1) The "right" way depends on many factors, but it's a good way to go. Lots of us use Access as a front end to SQL Server.

2) I would use the ODBC linked tables. There are good developers that like ADP's, but in my opinion the linked table solution is more flexible.

3) It should not lock the database, but could lock a record if 2 users try to edit the same record at the same time.
 
Thanks a lot.
 
If I only want our staff to enter data, or read reports etc for the database, instead of table, view or stored procedure design, should I set it up in sql server? I don't think I can do it in Access?
Is that correct?

THanks
 

Users who are viewing this thread

Back
Top Bottom