The Future of Access
Jon Sigler of Microsoft visited the Denver Access users group with some comments about where Access is going.
2005-02-24
3,281 reads
Additional Articles
Migrating Microsoft Access Applications to SQL Server
Microsoft Access targets individual information workers and small teams that use the Microsoft Office System to track, manage, prioritize, and act upon an increasing volume of business information. The data stored in these databases rarely justifies moving to a more robust platform until the application begins expanding into departmental scenarios. When this happens, it is worthwhile to consider moving the data into a more robust platform for enhanced reliability, scalability, and greater IT control. In most cases, the data can be moved through a process called "upsizing" while the Access application front-end continues to provide information workers with access to critical data. Microsoft has created resources in the following three categories to help manage Access data in your organizations:
2005-02-23
3,934 reads
Working with PowerPoint Presentations from Access Using Automation
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.
2005-02-23
1,852 reads
Access Development Best Practices
Online Chat with Chat Participants: Tim Getsch, Microsoft Access Program Manager, JP Bagel, Site Manager, Mike Wachal, Lead Beta Engineer, Mike Gunderloy, independent Access developer, Sanjay Jacob, Microsoft Access Program Manager, and Rita Nikas, Microsoft Access MVP Lead
2005-02-22
1,795 reads
Basics for Building Microsoft Office Access 2003 Runtime-Based Solutio
Jan Fransen reviews how to use the Microsoft Office Access 2003 Runtime with the Microsoft Access 2003 Developer Extensions so users without Microsoft Access 2003 installed can still use Access-based applications.
2005-02-22
1,094 reads
Performance Tuning Tips for Using Microsoft Access
If you are really interested in the fastest performance, don't use Access as a front-end to a SQL Server database. While Access is relatively easy to learn and fast to develop in, its performance if poor when compared to other front-end options. But if you like to develop in Access, or don't have any choice, then the tips on this page will help a little to boost your application's performance.
2005-02-22
3,035 reads
Slowly Changing Dimensions Are Not Always as Easy as 1, 2, 3
To kick off our first column of the year, we're going to take on a challenging subject that all designers face: how to deal with changing dimensions. Unlike most OLTP systems, a major objective of a data warehouse is to track history. So, accounting for change is one of the analyst's most important responsibilities. A sales force region reassignment is a good example of a business change that may require you to alter the dimensional data warehouse. We'll discuss how to apply the right technique to account for the change historically. Hang on to your hats — this is not an easy topic.
2005-02-21
1,868 reads
Installing and Configuring SQL Server Reporting Services
In this chapter, we discuss various installation setups you can use to install and configure Reporting Services. For the most part, this process is managed by the Setup.exe installation wizard, so expect to be prompted for a number of configuration options that determine how, where, and whether each segment of the Reporting Services package will be installed. We know that there are a variety of ways to install Reporting Services, so we've tried not only to address the common case, but also provide hints and techniques to be used for some of the more sophisticated installation scenarios. To make this process as painless as possible, we've broken this chapter down into several sections:
2005-02-18
3,426 reads
MDX Essentials: The CROSSJOIN() Function: Breaking Bottlenecks
In this article, we will return to a function we introduced in an earlier article, CROSSJOIN(), whose mission it is to combine two sets of dimension members into one. We will discuss how CROSSJOIN() works in general, and then discuss how its performance can become an issue in medium to large-sized data sets. We will then undertake a multiple-step practice example intended to assist us in gaining an understanding of the issues, before exposing approaches to minimizing the performance overhead that we can encounter in using CROSSJOIN() to reach our reporting and analysis needs.
2005-02-17
2,074 reads
The HAVING and GROUP BY SQL clauses
This month's topic is one that often baffles inexperienced SQL coders. We will look at the GROUP BY clause, and then the difference between conditions placed in the WHERE clause, and the HAVING clause. I have used MySQL to test all of the examples, but most of them should work without any problems on other DBMS' too.
2005-02-16
4,182 reads
Blogs
TempDB Internals – What’s New (SQL Server 2016 to 2022)
By Vinay Thakur
I wrote about TempDB Internals and understand that Tempdb plays very important role on...
Blog a Day – Day 2: Generative AI, Multimodal Systems, and Agent AI
By Vinay Thakur
continuing from Day 1 where we covered the history of AI and GPT family,...
A Wellbeing Day at Redgate
By Steve Jones
It’s a day off for Redgate today. This is our annual wellbeing day, where...
Forums
A Quick Restore
Comments posted to this topic are about the item A Quick Restore
Guarding Against SQL Injection at the Database Layer (SQL Server)
Comments posted to this topic are about the item Guarding Against SQL Injection at...
Question of the Day
A Quick Restore
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers