Access can be a very quick and easy to use tool for working with SQL Server data and for quick and dirty projects, it might be the best tool. But there can be performance issues at times and Andy Warren digs into some of these based on some analysis of what Access does behind the scenes.
A few months ago, I posted an article here at DBJ named How to Pass Access Data Across the Web. One reader expressed concern over using the Microsoft Internet Explorer library because of security issues. While I do not share his fear, I appreciate that others might, so I began to think about how the process could be enhanced by substituting a Web Service for the traditional ASP/Querystring web page approach described in the article. What follows is the fruit of those labors.
The solution described below should probably not be considered a "best practice" but it works. It came to life as I was pondering the following conundrum: How can I pass a little bit of data from an internal Access application behind a firewall out to a public web site in real time?
Learn how to bind a form dynamically to a recordset created from an XML file. This simple application can be the starting point for a powerful solution for your customers and should be considered a part of your arsenal when developing Access application.
SQL Server 2000 and Access databases are two technologies closely linked with the new Access ADP format using SQL Server as the basis for the code. Access Projects are also a way to closely link the two products together and take advantage of each to produce an application very easily. Author Kathi Kellenberger brings us part 3 of her Access series with a look at Access Projects.
Create a PowerPoint slide presentation from scratch using Access data. In addition, display and control a slide show from within an Access form. Walk through the solution and explore ways to extend the sample for your own applications.