Hi Tiang Yes - that is a good scenario where MS Access can be of benefit. For example - you run the report wizard. It asks the user the following
1. Table/Query to use 2. Fields on the report 3. Sorting or grouping 4. Totaling And it can then churn out a report that can be used immediately or expanded on. You can build quick apps in MMS Access as well like simple data entry. Or build queries that link together a lot of tables. I look on it as a sort of Database Glue - where you can merge all sorts of info together quickly for a test run, and then proceed to developed something more permanent later. One of the great confusions re MS Access is that people mix the name for both the Database and the Application. Technically the database layer is the JET engine, and MS Access is the application. JET has a number of issues, 64 bit compatibility, speed, size of the database, and locking/corruption issues as well. Also because it is so easy for managers to build small applications (hence my recommending R/O access) you can get a lot of terrible code out there from learners and beginners. Or some major DB corruption However the MS Application still works very well re chatting to other databases. One downside (unavoidable) is that if you wish to join tables from different databases then MS Access will do the join in memory so speed will be a factor. But the simple fact that you CAN join between different databases makes it a very powerful little helper. I hope this helps settle the confusion Dave -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Tiang Cheng Sent: Wednesday, 14 April 2010 12:30 PM To: ozDotNet Subject: RE: [OT] MSAccess developer wanted >Another good thing about MS Access is that it can be easy to teach a non DBA >or programmer to use. For example I can create a low level DB user who only >has read access. Link to the DB using MS Access and this user, and I can >give this to a manager who can have HOURS of fun crunching stats... leaving >the programmer to do more productive tasks. That sounds pretty awesome. Is this a scenario where we can give non-technical users access to generate their own query reports based on data in MSSQL? Tiang
