The Local
provider, IOM provider, OLAP provider, and
SAS/SHARE provider are
available in both 32-bit and 64-bit versions. On a 32-bit Windows
system, the 32-bit version of a provider is used. On a 64-bit Windows
system, a 64-bit application uses the 64-bit version of a provider.
For customers that choose to leave applications in 32-bit, but run
them on a 64-bit Windows system, the 32-bit application uses the 32-bit
provider version, and both run in the WOW64 compatibility environment.
The Base
SAS provider remains 32-bit. For customers in a 64-bit environment
that want to use the Base SAS provider for local data access, SAS
recommends using the 64-bit version of the
SAS/SHARE provider instead.
The
SAS/SHARE provider offers all the features of the Base SAS provider. When using the
SAS/SHARE provider to access local data,
you need to use PROC ODBCSERV to start a single-user server. A license
for
SAS/SHARE is not required when using the
SAS/SHARE provider and
PROC ODBCSERV.
For more information, see Connecting to Local Data (Single-User Server).For customers
that are programming to the OLE DB interface (as opposed to ADO or
.NET Framework), Microsoft made a change to the OLE DB header file
to accommodate 64-bit environments. This change might require revision
to the application code if you plan to migrate the application to
the 64-bit environment. For more information about the change to the
OLE DB header file, see
INFO: OLE DB Header File Changes for 64-Bit Platform Programming.
For applications
that are programmed to the ADO and .NET Framework interfaces, migration
challenges are largely overcome. The data access interfaces are designed
to avoid the details of 32-bit and 64-bit programming. Use the latest
software development tools available from Microsoft when migrating
your application from 32-bit to the 64-bit environment.
The following
list identifies Microsoft resources that you might find valuable for
understanding the WOW64 compatibility environment and for migrating
your applications: