If unable to connect to SQL Server standard or Express edition (using 2008) from another machine using SQL management studios try the step in this Blog post  (from a previous post) and if that still does not resolve the issue, like in my case today, them it is the firewall. Make sure you open UDP port 1434 on the server machine. That took care of the connection problem in my case. This page from Microsoft’s support site gives more details on what else to look for –> Microsoft SQL Support.

The above helped resolved the following connection errors.

NOTE: Connecting to a default instance of SQL Server (not the Express Edition) does not required the instance name, only the server name like so.

I recently upgraded to Access 2010 at work and had to open one of my old databases to run some macros. This database had been built in Access 2003 and was now being open in Access 2010. For the most part, I was expecting all queries and macros to work , and must say they did, except for one in particular: The ImportExportText macro. This macro was exporting text to an excel workbook and while it ran it came up with the following error message: “The text file specification ‘|’ does not exist”… To resolve this, head over to the KB Article ID: 2581495.

Here is what worked for me:

  1. I applied the June 2011 cumulative update for Microsoft Access 2010 – http://support.microsoft.com/kb/2544022
  2. I edited the macro in design view and re-selected the proper text specification.
  3. Saved the macro.

Make sure you do step 2 & 3 otherwise you will continue to get the error. After the update you will see the text specification has changed to a number, like 1 or another ramdom number. You must change it back to the correct one, which in my case was: <name of the macro> import specification.

Hope this helps.

After hours of trying to connect to my SQL Server 2008 Express install I  came across this Post. Thank you Mr. Luangaroon, you have save me more hours of searching through the  Microsoft site.

If you are receiving the following message, or one similar to it (error 53, 67, 17..etc) while trying to make an ODBC connection to your SQL Server, take a look at the steps on this post. It helped me.

Connection failed:
SQL State: ‘01000’
SQL Server error: 11001
[microsoft][ODBC SQL Server Driver][TCP/IP

Sockets]ConnectionOpen (Connect()).
Connection failed:
SQL State: ‘08001’
SQL Server Error: 6
[microsoft][ODBC SQL Server Driver][TCP/IP Sockets]Specified
SQL Server not found.

Click here –> Linglom’s blog

I use this to validate data I had entered in a number field in a small tracking DB I recently worked on. It came in very handy.  Make sure you replace the table and DB name with the names you are using for your DB and copy the rest as it is in the module:

Private Sub AccNumberBox_BeforeUpdate(Cancel As Integer)
On Error GoTo ACC_Tbl_Err
Dim CurDB As Database, ACC_Tbl As Recordset, SQLStmt As String

Set CurDB = CurrentDb
SQLStmt = “Select AccNumber FROM ACC_Tbl WHERE AccNumber = “”” & Me!AccNumber & “”””

Set ACC_Tbl = CurDB.OpenRecordset(SQLStmt)

If Not ACC_Tbl.EOF Then
MsgBox “This Batch Number has been entered. Please enter unique value.”, vbCritical, “Duplicate Entry”
Cancel = True
End If
Set ACC_Tbl = Nothing
Exit Sub

MsgBox “Error is ” & Err.Description & ” Entering new Batch Number”, vbCritical, “”
Exit Sub
End Sub