Running Classic ASP Applications on IIS 7.0 and IIS 7.5

This article covers the folowing topics:

• Classic ASP Applications on IIS 7.0 and IIS 7.5 Overview
• Classic ASP Not Installed by Default on IIS 7.0 and IIS 7.5
• Classic ASP Script Error Messages No Longer Shown in Web Browser by Default
• Using Failed Request Tracing to troubleshoot
• Classic ASP errorsClassic ASP parent paths are disabled by default
• Using Classic ASP with Microsoft Access Databases on IIS 7.0 and IIS 7.5
• APPL_PHYSICAL_PATH Server Variable on Windows Vista RTM
  

Read this article

Registering 32-bit DLL on Windows Server SBS 2008 64-bit

Recently I'm installing a 32-bit application on a fresh installed Windows Server SBS 2008 which only comes in 64-bit version.
This application that I'm installing is requiring a DLL file to be registered on the registry using the regsvr32 command.
Here comes the problem with registering 32-bit DLL since 32-bit application see different "system32" in Windows Server 64-bit. 32-bit application will see %windir%\syswow64 as their "system32" directory in 64-bit OS, while 64-bit application will use the
%windir%\system32.
So to register the 32-bit DLL on 64-bit
Windows Server we need to call the 32-bit version of regsvr32 which located on
%windir%\syswow64, for
example:

C:\Windows\SysWOW64\regsvr32.exe .dll

Resource : Markus Blog What’s going on Internet?

How To Execute DB2 SQL Parameterized Stored Procedures from a Visual Basic .NET Application Using StarSQL

How To Execute DB2 SQL Parameterized Stored Procedures from a Visual Basic .NET Application Using StarSQL

Abstract
This document describes how to execute DB2 SQL parameterized stored procedures from a Visual Basic .NET application using the StarSQL software and the Microsoft .NET Framework Data Provider for ODBC.

Read this article Read this article Read this article Read this article

Download Free E-Book Introducing Windows Server 2008 R2 From Microsoft

Microsoft has released yet another free e-book named Introducing Windows Server 2008 R2 and the book is available to download via Microsoft Download Center
This book covers every aspect of Windows Server 2008 R2 in nine chapters and approximately 200 pages.

Go to download page

Also you can view this book an diwnload it from this link

What is the WINSXS directory in Windows 2008 and Windows Vista and why is it so large?

A commonly asked question among people looking at a Windows Vista or Windows Server 2008 installation is “why is the WinSxS folder so big?!” To answer that question I need to first describe componentization, and how components are managed in Windows Vista.

Read this article Read this article Read this article Read this article

Implementing a Provider Independent Data Access Layer in .NET

For applications built using Microsoft DNA, ADO provided one of the easiest ways of data access. ADO gave developers, COM based API for data access and using ADO components, a multitude of data sources could be accessed. The main reason for this was that ADO used the OLEDB provider internally to connect to data sources and more importantly there existed an OLEDB provider for ODBC. This meant that developers could use ADO to connect to ODBC sources using DSNs in their connection strings as well.

Data access in ADO.NET is not quite the same. Unlike ADO which just used OLEDB, ADO.NET provides many independent providers targeted to specific data sources. For example, the SQLClient provider deals specifically with SQL Server 7 and SQL Server 2000 as the data sources. The ODBC.NET provider deals with access to data sources using ODBC and DSNs. Likewise the OLEDB.NET provider is used to connect to OLEDB data sources. Also, there exists a separate .NET provider for Oracle databases.

Having independent providers for data access has the advantage that each provider is tuned for a specific data source and provides the most efficient access for that data source. For example, SQLClient is by far, the most efficient way of accessing SQL Server 7 or 2000 data sources. But the disadvantage here is that developers may have to decide on a particular provider and the generic way of access is not as easy as in ADO.

Now, what if the decision of selecting a provider is taken as late as application runtime? How should the data access layer (let�s call it DAL) be implemented so that applications that use the DAL be unaware of the provider being used and still work seamlessly with the DAL? This article deals with the design and implementation of the DAL which answers the above questions.

Read this article Read this article Read this article Read this article

Create contacted string fields via Crystal reports for group and print detail records in group summary by using running total.

I was asked to write a report that calculates daily transportation cost.
The report should be grouped by Date, Driver.
The report should contain daily destinations combined together for every driver.
Actually the report should contact driver destinations together
The report format is as follow

Date	Driver	Km	Cost	Destinations
05.02.10	01-John	330	2,000	Town1-T2,T2-T3
05.02.10	02-Mohammed	450	3,500	T3-T4,T4-T1
Total for	05.02.10	780	5,500

However my transport file contains one record for every destination as follow:

Date	Driver	Km	Cost	Destinations
05.02.10	01-John	150	800	Town1-T2
05.02.10	01-John	180	1200	T2-T3
05.02.10	02-Mohammed	250	2000	T3-T4
05.02.10	02-Mohammed	200	1500	T4-T1

In order to write this report I declared 2 summary Groups
1:- Date 2:-Driver
Every group has 2 totals fields Km and Cost.
In order to print just total I hide the details and groups headers (GH1,GH2,D).
However the problem is how to print the destinations .

Figure 1

In this report format I declared 2 groups 1:- Date 2:-Driver and every group has 2 totals fields Km and Cost.

In order to create contacted field that contain all destinations I have to

declare 3 calculated fields

1:-Flds that clear contacted field at the beginning of every group (@Desrest).For this purpose I will use whileprintingrecords function and reset the variablethat contains the contacted fields (S).

The field formula is as follow :

whileprintingrecords;

stringvar s;

s:='';

This field should be replaced at the beginning of the group.

2:-Running field that contact destinations.(@des1).

This field contact destinations fields.

Actually for every record contact destinations to previous contacted fields.

The destination fields is {HOVDST.HDTOPLC} and the group field is S.

Also we use whileprintingrecords method to group records.

whileprintingrecords;

stringvar s;

s:=s+trim({HOVDST.HDTOPLC})+" , ";

This filed should be replaced at report detail.

3:-Total fields to be displayed in the report (@desdsp).

We have to declare this field and also we will use whileprintingrecords method.

The field formula is as follow :

whileprintingrecords;

stringvar s;

This field should placed at driver group footer GF2 and it is very important to declare this field.

See also WhilePrintingRecords and WhileReadingRecords.