• Call a SQL Server stored procedure from a Grid
• Call User Defined Scalar Functions in SQL Server Oracle
• Create a LocalDB Snapshot
• Creating a Grid Based on a Microsoft Access Table or View
• Creating a Grid for Microsoft Access Using the SQL Builder
• Dynamically Connecting to a Database Using an Encrypted Password
• Dynamically Construct SQL Statements
• Export SQL Query to Excel
• Export Tables from a Database
• How to Connect to SQL Server from 64-bit Windows
• Import mixed format columns from Excel with AlphaDAO
• Improve SQL Server Query Performance Using Indexes
• Mark Records Deleted Without Deleting Them
• Use Output Arguments with Stored Procedures

How to Connect to SQL Server from 64-bit Windows

Description

Alpha Anywhere SQL Server interface is a wrapper around Microsoft s SQL Server ODBC drivers (there are now three versions). If you are able to create a DSN with the Microsoft ODBC manager, then you will be able to connect with Alpha Anywhere as well.

Please confirm that the following are in place:

1. The Microsoft ODBC driver for SQL Server is installed on the machine where Alpha Anywhere is running. Note that there are three different drivers from Microsoft. This is new since SQL Server 2005. Previously, updating the MDAC (Microsoft Data Access Components) package kept things current.

   • SQL Server 2000 - MDAC (the classic ODBC driver)

   • SQL Server 2005 - Native Client version 9

   • SQL Server 2008 - Native Client version 10

2. Make sure that TCP/IP is enabled as a protocol on both the client and the server machines. This part is more complicated. I suspect that Microsoft sets it up for local use deliberately.

   • 1. Select the Administrative Tools option on the Windows Control Panel.

   • 2. From there, choose Computer Management and open the item in the tree labeled Services and Applications .

   • 3. Finally, select SQL Server Configuration Manager .

   • On the Client Side

   • 1. Select SQL Native Client 10.0 Configuration (32bit) (for SQL Server 2008). Again, you want to make changes to the 32-bit configuration.

   • 2. Select the Client Protocols item.

   • 3. Make sure TCP/IP is enabled (you can right-click on the item to enable it).

   • 4. Double-click on the item to open the properties dialog.

   • 5. There will be a single dialog showing the port this should default to 1433, but you may want to check it.

   • On the Server Side

     1. Select SQL Server Network Configuration (32bit). Again, you want to make changes to the 32-bit configuration.

   • 2. Select the Protocols for SQLEXPRESS item, or whatever name is appropriate for the instance you are configuring.

   • 3. Make sure TCP/IP is enabled (you can right-click on the item to enable it).

   • 4. Double-click on the item to open the properties dialog.

   • 5. On the Protocol tab, make sure Enabled is set to Yes and Listen All is set to Yes

   • 6. There is a separate tab labeled IP Addresses . Note that this is plural.

     • You will need to make sure that the various IPV4 and the IPV6 ports are both Active and Enabled.

     • This is especially true of the machine address IP (not just localhost 127.0.0.1).

3. You are able to create a connection from the Microsoft ODBC Data Source Administrator to SQL Server working locally on the server. Do this by creating a System DSN for the driver you have installed. The driver will prompt you for connection information. Use the test button at the end to confirm you have a connection.

   If you are running a 64 bit version of Windows, you will need to run the 32-bit version of the ODBC Data Source Administrator typically found in c:\windows\syswow64\odbcad32.exe