HELP, PLEASE! Unlink a table

N

Nona

I have a new database ready for the network that I split using the wizard.
One of the tables in this db was copied from another db and now refuses to
recognize the new BE in spite of repeatedly going through the automatic
Linked Table Manager. I get an error message saying it can't find this table.

How do I unlink this table? I read a previous question/answer that suggested
deleting the table from the secondary db, but I didn't really understand
this. What is the secondary db?

Many thanks for your help!
 
A

a a r o n _ k e m p f

it sounds to me like you need to get rid of linking entirely--
I think that linking is too complex for most developers of MS Access.

I moved to SQL Server and Access Data Projects about a decade ago--
because I saw that 'all databases automagically link- like they
should- when they are on the same server'

because a single db server fills the needs of 99% of the developers in
this group-- it makes a lot of sense to me-- to just move to SQL
Server
 
W

Wayne-I-M

Sorry - forgot to say - also have a look at the good advice given John Vinson
in the same thread (use the link gave in my answer above)
 
P

Pete D.

First backup everything. Then delete the linked table under the tables tab
in Access. Then close everything. Open access and relink your tables using
the wizard. Should cure your problem.
Pete D.
 
T

Troll Chaser

Wrong again!

So you're saying that ODBC connections and OLEDB connections can't break?
Not only can they break, but troubleshooting a broken DSN requires
rebuilding it, often multiple times.

The real answer is to simply delete the Access table link and relink it to
the new source. Simple and quicker than trying to resolve any SQL-Server
connection problem. Only a retard would suggest rewriting an entire database
to handle a simple linking problem. What a BOZO you are!

it sounds to me like you need to get rid of linking entirely--
I think that linking is too complex for most developers of MS Access.

I moved to SQL Server and Access Data Projects about a decade ago--
because I saw that 'all databases automagically link- like they
should- when they are on the same server'

because a single db server fills the needs of 99% of the developers in
this group-- it makes a lot of sense to me-- to just move to SQL
Server
 
A

a a r o n _ k e m p f

wtf _ARE_ you talking about?
SQL Server connections don't fail-- things 'just work'.

I only have a single connection-- FILE, CONNECTION, SERVERNAME +
DBNAME

I don't need to set the connection strings in 200 different places--
and more importantly; I don't have to use an obsolete DAL in order to
do it.

DAO wasn't included with Office or WIndows for most of a decade.

Only a retard would use DAO for anything.
 
N

Nona

Got everything working beautifully! (without Aaron's help!)
Thanks very much! This is a wonderful service. Hope you all get paid well!
 
P

Pete D.

This is a group where many experts, and beginners donate free time to help
others in the newsgroup. Now that you know how to correct that problem come
back and teach others when your not busy. Just answer the questions for
others that you know. Glad you got it fixed.
 
J

John W. Vinson/MVP

Got everything working beautifully! (without Aaron's help!)
Thanks very much! This is a wonderful service. Hope you all get paid well!

Gratitude such as this is the only payment the volunteers here need or
expect. Thank YOU!
 
A

a a r o n _ k e m p f

Jet programmers average about half of what SQL developers / DBA make.

There's just not enough demand for high-level Jet developers.. anyone
that really cares about their data moves to SQL Server

-Aaron
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top