Color scheme: Light
You are here: start » en » Documentation » Microsoft Access development tools » WKL Forms Object Library » WKL Forms Object Library troubleshooting » Tables aren't linked at startup

Tables aren't linked at startup

EnsureLinks (or RelinkAll, Relink, Refresh all in the designer) raises wkeSourceError with a message like “Profile “PROD”: 3 tables linked, not linked:” followed by one line per table, or a login dialog box of the ODBC driver appears at startup.

Environment

WKL Forms Object Library with WklLinkManager, in ACCDB or ACCDE files or the Access Runtime.

Cause

The link manager links every table it can and lists the others, one line per table in the form “tblName: reason”; LastMessage holds the same lines. By reason:

Line saysCause
“A local table of this name is in the way; it is not replaced.”A local table has the configured LocalName. The link manager never replaces local tables, because that would delete data.
The driver's message, for example a login or network errorThe source refused the link: server not reachable, database missing, login failed, or the driver named in Driver isn't installed for the bitness of Access.
Error 3423 (“You cannot use ODBC to import from, export to, or link an external Microsoft Access or ISAM database table to your database.”)The connection points to an Access database through ODBC. Access doesn't link Access databases through ODBC.
The connection "Sales" has no row for the profile "PROD". or There is no connection with the ID 7.No row of USysConnection has the connection's name and this profile (or no profile), or ConnectionID points to a deleted row.

A login dialog box at startup means that a connection has neither the Windows sign-in nor a stored password, so the driver asks for the login when the table is linked.

Resolution

  1. Read LastMessage (or the list on the designer's Check and synchronize page) and handle each table by its line.
  2. Local table in the way: rename or delete the local table, or change LocalName in USysLinkedTable.
  3. Source refused: select the connection on the Connections page and click Test connection; it shows the driver's message without a dialog box. Check server, database and the driver name; ODBC drivers are installed per bitness (32-bit Access needs the 32-bit driver).
  4. Access database as back end: link Access back ends with the Linked Table Manager of Access, not with ODBC.
  5. Missing connection: add a row for the profile, for example with Copy profile … on the Profiles page.
  6. Login dialog box: use the Windows sign-in, or choose another option deliberately (How to: Choose how linked tables log in).
en/wiki/msaccess/comctl/troubleshooting/tables-not-linked-at-start.txt · Last modified: by Wolfgang van der Stille