Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6203939
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 24, 20262026-05-24T05:00:11+00:00 2026-05-24T05:00:11+00:00

Microsoft Access 2003 database (.mdb) containing a linked table which connects via ODBC to

  • 0

Microsoft Access 2003 database (.mdb) containing a linked table which connects via ODBC to a backend Microsoft SQL Server 2008 table.

When I enter design view for the linked table, then view the Properties field, I can only see the first 255 characters (specific fields replaced with hyphens):

ODBC;Description=------------------------------------;DRIVER=SQL Server;SERVER=----;APP=--------------------------------;WSID=---------;DATABASE=------------------;StatsLog_On=Yes;StatsLogFile=--------------------------------------------------------------

When I print the DAO field using the VBA Immediate Window (table name ommitted: “print CurrentDb.TableDefs(“———–“).Connect”), I see a prefix plus 254 characters (prefix “ODBC;Description=” plus 254 characters, plus, presumably, a one-byte null character):

ODBC;Description=------------------------------------;DRIVER=SQL Server;SERVER=----;APP=--------------------------------;WSID=---------;DATABASE=------------------;StatsLog_On=Yes;StatsLogFile=------------------------------------------------------------------;Trusted_Co

How do I view the entire text of the ODBC connection string?

We experience an issue where the SQL Server server logs show error “Login failed for user “{user}”. Reason: Could not find a login matching the name provided. [CLIENT: {ip address}]”

I am attempting to confirm the full string “Trusted_Connection=Yes” is part of the stored string.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-24T05:00:12+00:00Added an answer on May 24, 2026 at 5:00 am

    The problem turned out to be a 255 character Microsoft Access (2003/2010) limitation on the ODBC connection string.

    I removed the ODBC references to StatsLog ant re-linked all the tables within the Microsoft Access database. It has been one week and the DBA team reports no further server log errors.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have an Access 2003 database that connects to a SQL Server 2008 box
I have been successful in querying a Microsoft Access 2003 database (.mdb file) and
I am upscaling an access 2003 database to SQL Server Express 2008. The tables
What are the implications of running a Microsoft Access Database in both 2003 and
This SQL query was generated by Microsoft Access 2003, and works fine when run,
Microsoft Access is a slick way to access data in a MS SQL Server
Does Microsoft Access have Full Text Search? I know that MySQL and SQL Server
I need to automate the migration from an Access (2003) to an SQL Server
Errors Database administrators report Microsoft SQL Server 2008 server-side error Invalid Login (error 18456,
I have an Microsoft Access 2003 ADP, which uses a bound main form with

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.