|
This is exactly the environment we run, because so many
of our data-maintainers are used to Access, and I don't particularly want to
develop complete DBMS w/CF.
There are at least two different ways of using Access to front-end SQL
server databases; we use Access Data Projects, which, to use a
much-too-simplistic analogy, is like a window to the SQL database.
Each project connects to the SQL database and pulls in SQL Server objects (i.e.
tables, views, stored procedures). In addition, w/in each project, users
can create Access objects (i.e. forms & reports). Obviously SQL Server
objects are shared by all projects that connect to the same database, while
Access objects are not shared.
The main snags we've hit tend to revolve around security
settings/permissions and table names. In addition, because projects cannot
be opened simultaneously by more than one user and because forms cannot be
shared automatically by all projects, there is a bit of a management
issue. Everytime I update a form for others to use, I have to import it
into all relevant projects. However, this is only really an issue when you have
multiple users of databases.
You probably want to try getting Rick Dobson's book, SQL Server with Access
2000 (a WROX book).
Karen R. Harker, MLS
UT Southwestern Medical Library 5323 Harry Hines Blvd. Dallas, TX 75390-9049 214-648-1698 http://www.swmed.edu/library/ >>> [EMAIL PROTECTED] 11/29/01 1:45:11 PM >>> We currently have an application that is maintained by and used by one user using Microsoft Access. He generates reports from his database to manage the data and to mail the reports out to internal customers. We would like to migrate the database tables to SQL Server and have the reports that he mails out become web pages. It should be easy to migrate the database tables and data, and we'll use CF to write the web page reports that the customers will use, instead of receiving paper reports. The person who manages the data still wants to use Access to run his special analyses and do data maintenance through Access. Is this do-able? Can Access front-end SQL Server database tables? Are we likely to have to make many changes to the Access reports or forms? (The sophistication of what's in Access is mid-level, at best.) What stumbling blocks might we hit? Thanks, -- David ------------------------------------------------------------------------- This email server is running an evaluation copy of the MailShield anti- spam software. Please contact your email administrator if you have any questions about this message. MailShield product info: www.mailshield.com ----------------------------------------------- To post, send email to [EMAIL PROTECTED] To subscribe / unsubscribe: http://www.dfwcfug.org |
- Access Front-Ending SQL Server Database Goldstein, David
- RE: Access Front-Ending SQL Server Database Dave Cahall
- Re: Access Front-Ending SQL Server Database Bruce Sorge
- RE: Access Front-Ending SQL Server Database Goldstein, David
- RE: Access Front-Ending SQL Server Database Dave Cahall
- RE: Access Front-Ending SQL Server Database Schreck, Tom
- Karen Harker
