Archive for July, 2005

July 2005 Update of the Microsoft Excel 2003 VBA Language Reference

Tuesday, July 19th, 2005

The Excel 2003 VBA Language Reference has been updated.

Welcome to the Microsoft Excel 2003 Language Reference. This reference contains conceptual overviews, programming tasks, samples, and references to guide you in developing solutions based on Microsoft Excel.

Publish date of this reference: July 2005 (version 2003)

Download the Microsoft Excel 2003 Language Reference

The reference contains the following sections:

What’s New Provides a list of new members by object and in alphabetical order.
Concepts Provides important concepts for developing custom Excel solutions.
Reference Provides reference materials for the Excel object model.

Source: Welcome to the Microsoft Excel 2003 VBA Language Reference

Migrating Excel VBA Solutions to Visual Studio 2005 Tools for Office

Monday, July 11th, 2005

Microsoft Visual Basic for Applications (VBA) is the programming environment and language for Microsoft Office that has been available for several years. Microsoft Office 2003 Editions have a new environment for building applications, called Visual Studio Tools for Office, which is based on the Microsoft .NET Framework.

Microsoft Visual Studio Tools for Office, Version 2003, offered many advantages over VBA, but Microsoft Visual Studio 2005 Tools for Office enhances these features for even more user productivity.

This article analyzes many solution migration issues that you may face when using the Visual Basic language to directly migrate a VBA solution to Visual Studio 2005 Tools for Office. The

Source : Migrating Excel VBA Solutions to Visual Studio 2005 Tools for Office

Changing AutoFilter Drop-Down Arrow Colors

Sunday, July 10th, 2005

Along with Pivot Tables, AutoFilter is one the Excel features I find most useful. I have always found that it a little hard sometimes to see which columns I am filtering on. Many times I have turned off the AutoFilter and then turned it back on in order to start from scratch.

Summary: When you use the AutoFilter capabilities of Excel (Data | Filter | AutoFilter), small drop-down arrows appear at the top of each column in your data table. The color of the drop-down arrows changes from black to navy blue if a filter is applied to the column. The color of the arrows cannot be changed, but there are workarounds that can be used to make filtered columns stand out better. (This tip works with Microsoft Excel 97, Excel 2000, Excel 2002, and Excel 2003.)

Source: Changing AutoFilter Drop-Down Arrow Colors

Microsoft Office Assistance: Using Access or Excel to manage your data

Sunday, July 10th, 2005

When to use Acess (database) vs. when to use Excel (spreadsheet).

When to use Access

Use Access when you:

  • Require a relational database (multiple tables) to store your data.
  • May need to add more tables in the future to an originally flat or non-relational data set. For example, if you want to keep track of customer information such as first and last names, addresses, and telephone numbers, but that information may grow to include actions by customers such as orders, then consider starting your data project in Access.
  • Have a very large amount of data (thousands of entries). For example, if you work in a large company and are required to store personnel information, then use Access.
  • Have data that is mostly of the long text string type (not numbers or defined as numbers).
  • Rely on multiple external databases to derive and analyze the data you need. For example, if you need to import or export data regularly from Access databases, it may make the most sense to work in Access to maximize compatibility.
  • Need to maintain constant connectivity to a large external database such as one built with Microsoft SQL Server.
  • Want to run complex queries. For example, if you work in a large company that takes customer orders, you might have to look up customer names stored in a SQL Server database while taking new customer orders in Access. You can maintain a connection to the SQL Server database from within the Table view in Access. When you add or look up a customer name, you are working against the SQL Server database, but the new order details you just took are stored locally in Access tables.
  • Have many people working in the database and want robust options to expose that data for updating. For example, Access offers data access pages for the more technical user and forms if you want to be more user friendly.
  • When to use Excel

    Use Excel when you:

  • Require a flat or non-relational view of your data (you do not need a relational database with multiple tables). This is especially true if that data is mostly numeric— for example, if you want to maintain a financial budget for a given year.
  • Want to run primarily calculations and statistical comparisons on your data— for example, if you want to show a cost/benefit analysis in your company’s budget.
  • Know your dataset is manageable in size (no more than 15,000 rows).
  • The key to your decision: Is the data relational or not?

    If you can store your data logically in a single table or worksheet, then do it. By logically, I mean that the data in each column is directly related and need only reside in a single, flat table in either Access or Excel. It should reside in and be updated in the same view. Data of this kind, contained in a single page or sheet (not multiple) is called flat or non-relational data. The personnel example above is a case in point. You would not store an employee’s last name in a table other than the one that stores the employee’s first name.

    “The most common task in Excel is the management of lists. If you can store your data logically in a single worksheet or table, then do it.”

    However, if your data needs to be stored in more than one table, then you need a relational database. Each table is basically a description of a type of data (such as orders for a customer). If you require a relational database, you’ve identified a one-to-many relationship in your data. For example, if you have a customer order database, one table will contain customer names and another will contain their orders. And a single customer can have many orders. Additionally, you might want to have another table for order details since each order can have multiple line items. Relational data is best stored in Access.

    Do you notice this direct correlation between the size of your data and the challenge you have in organizing it effectively? The more data you have, the more likely you are to store it in multiple tables in Access. To help manage your data and keep it accurate, Access and Excel provide you with unique identifiers. In Access, a primary key (an icon in the shape of a key visible in Design view of your table) uniquely identifies each record. In Excel, each row is numbered and each column is denoted by a letter, so each cell or range of cells has a reference such as B5. In life, you have a social security number. It’s the best unique identifier you have.

    “In Access, you have a primary key. In Excel, you have a cell reference. In life, you have a social security number. It’s the best unique identifier you have.”

    Source : Microsoft Office Assistance: Using Access or Excel to manage your data

    First Post to the Excel Blog

    Sunday, July 3rd, 2005

    This is the first, test post to the Excel Blog (www.excelblog.net).

    I am using WordPress 2.5+ along with the Revolution News Theme developed by Brian Gardner.

    I use Excel at work everyday. I am not an Excel or spreadsheet expert – but I am better than your average Joe in making Excel meet my needs.

    My purpose for creating and updating this blog is primarily for my own education. I am hoping that organizing my understanding on a weblog will smooth my path in becoming an expert.

    My goal is to organize resource related to Excel as an analytical tool and as a data and information management tool.

    I also hope that what I created will benefit others, as many Excel websites and blogs have been useful to me.

    I believe I will start out slow, but hopefully will be able to evolve into something that is more than a Excel tips bookmarking site.

    Let the journey begin.