VO Conversion

The Visual Studio debugger is an extremely powerful tool, sometimes however it is more convenient to use output statements so that the application can keep on running while you inspect what’s going on behind the scenes.

Wouldn’t it be nice if all business e-mail automatically got archived in your on-line document storage? Filing every e-mail with the proper client and accessible for the entire organisation while also applying proper security trimming.

Introduction to building Reports using SQL Server Reporting Services (RS) and Visual Studio (included with RS). Microsoft SQL Server 2000 and 2005 come with functionality to develop distribute and run web-based reports. Typically these reports can be view

This session is devoted solely to the migration process itself. We need to develop a clear strategy to get to SQL and we will be giving some things up we will crave just minutes later. We may also change things that cause our code to break so being able to roll back our changes is very important. This is only possible if we were structured in our approach.

Moving your code is also as much about moving your users because it will be your users that will remind you about what you have taken from them! But the news is certainly not all bad and very quickly you will be able to offer integrity and stability such as was never available with DBF. You will also be able to trade some performance and flexibility losses with performance gains that should eventually win over your clients

The 5333 is a dynamic memory error and is not the end of life as we know it. However, it has been a significant source of frustration and often feels that way for many developers, especially when moving to the more restrictive compiler environment of VO 2.7b. The 5333 error is all about dynamic memory and the way it is managed… or mismanaged. The reason is appears difficult to track is because it occurs when an improper reference to dynamic memory occurs. In an event driven environment with a garbage collector active, this will often occur much later than the piece of code which set up the incorrect reference. The garbage collector itself often triggers such issues and because this too appears asynchronous in execution, tracking the error often seems impossible. Well there is good news. With a few simple tools and some understanding of dynamic memory, you can rest assured that you can eradicate this type of error, or at very least, provide yourself with mechanisms to detect and control them.

The aim of this paper is to train you to the point where you have to knowledge to avoid the situations likely to cause dynamic memory errors. You will need to know something about dynamic memory and also have some debugging tools to assist your research. The format of the material includes the following discussions:

• What dynamic memory is
• All about the Garbage Collector
• A profile of the 5333 error
• Common situations which cause a 5333 error
• Tools to inspect application performance
• Error handlers to trap 5333 errors

We will demonstrate some important integration aspects, our aim is to show how we can employ MS Office products from our VO desktop application. This is about integration: about making our applications smarter and by making MS Office products smarter, mor

Getting started with VO and Outlook using the VO2Outlook class library.

Windows XP SP2 introduced a new API for managing the Windows Update Service. As with many a new API this one is com-callable and therefore can be used from Visual Objects applications.