how do i delete a relationship in access

A

alan fullard

can any one help i want to delete a relationship in access as online help is
not very helpfull
 
D

Daniel Pineault

Nothing could be easier.

Open the relationship 'viewer'
Click on the relationship between the two tables you wish to delete (it will
become bold)
Press the delete key on your keyboard

For an introduction to relationships you may want to take a look at
http://www.functionx.com/access/Lesson12.htm
--
Hope this helps,

Daniel Pineault
For Access Tips and Examples: http://www.cardaconsultants.com/en/msaccess.php
If this post was helpful, please rate it by using the vote buttons.
 
B

Brendan Reynolds

alan fullard said:
can any one help i want to delete a relationship in access as online help
is
not very helpfull


Manually or programmatically? Manually, in the Relationships window,
right-click the relationship line between the two tables and choose Delete
from the shortcut menu. Programmatically, you can do it via DAO. You'll
first need to know the name of the relationship. The following procedure
should provide enough information to identify it ...

Public Sub ListRelationships()

Dim db As DAO.Database
Dim rels As DAO.Relations
Dim rel As DAO.Relation

Set db = CurrentDb
Set rels = db.Relations
Debug.Print "Name", , "Table", "Foreign Table"
For Each rel In rels
Debug.Print rel.Name, , rel.Table, rel.ForeignTable
Next rel

End Sub

Once you have the name of the relationship you want to delete, deleting it
is easy ...

CurrentDb.Relations.Delete "NameOfYourRelationshipHere"
 
A

aaron.kempf

Warning!!

DAO for _ANY_ reason whatsover-- is not reccomended; it was not
included with Windows or Office for almost a decade.
DAO is a memory leak waiting to happen.

If your variables won't clean up after themselves; then move to
someone that will.

-Aaron
 
R

Roger Carlson

All you have to do is open _ANY_ code window in a brand new Access 2003
database and go to Tools>References to see that this is patently false.

--
--Roger Carlson
MS Access MVP
www.rogersaccesslibrary.com

Warning!!

DAO for _ANY_ reason whatsover-- is not reccomended; it was not
included with Windows or Office for almost a decade.
DAO is a memory leak waiting to happen.

If your variables won't clean up after themselves; then move to
someone that will.

-Aaron
 
T

Tony Toews [MVP]

Warning!!

DAO for _ANY_ reason whatsover-- is not reccomended; it was not
included with Windows or Office for almost a decade.
DAO is a memory leak waiting to happen.

If your variables won't clean up after themselves; then move to
someone that will.

Absolutely wrong.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
 
A

a a r o n . k e m p f

re:
If your variables won't clean up after themselves; then move to
someone that will.

How is that wrong? I mean _HONESTLY_. I don't need to cleanup
variables-- they grow out of scope and I'm done with them. It's a
perfectly logical statement.

Please explain- oh mightly Tony-- how you can just magically say it is
wrong-- when it is obviously a compelling EVIDENCE to continue to move
away from DAO. DAO was niether included or upgraded in a decade.

-Aaron
 
A

a a r o n . k e m p f

I'm not so sure that is true.

It's not called DAO in 2007.
and it's not included - by default - in 2000 or 2002?

How many months was that between 2000 and the release of 2003?

How many more morsels of functionality can I do with ADO than you kids
can do with DAO?

How about _SHAPING_ the data?

Oh yah-- you guys don't know about that stuff.

DAO wasn't included with any version of MDAC from 2.6 upwards.
WIndows XP comes with MDAC 2.6.

I don't see-- what is wrong with my statement.

Everything that I said is 100% accurate.

_SORRY_.

I just won't be bullied into submission.

Take your JET or SHAREPOINT and _SHOVE_IT_.

-Aaron
 
P

Pete D.

Proven wrong, can't hit the basket and you want the points? Read each of
the replies to you over the years, those are the points you should take.
and for the record; I'll gladly take the points in this one

-Aaron
 
A

a a r o n . k e m p f

Is it called DAO?

Is it included - by default - in a decade's worth of databases?

Whatever kid.

With DAO, you've _GOT_ to clean up after your objects.

If you've got to

.CLOSE
or
Set dbs = Nothing

THEN IT IS TIME TO MOVE INTO A BETTER LIBRARY.

Dao is just a sloopy piece of crap library.
It has no benefits over ADO.

ADO provides DDL for creating objects-- a much better- more more
transparent route- than Access.

-Aaron
 
A

a a r o n . k e m p f

DAO for _ANY_ reason whatsover-- is not reccomended; it was not
included with Windows or Office for almost a decade.
DAO is a memory leak waiting to happen.


If your variables won't clean up after themselves; then move to
someone that will.
 
P

Pete D.

Wrong, what an expert you are, I have used all versions and all had DAO. It
wasn't default for a version but seems to me, it is again, so what planet
are you on? MS isn't stupid, apparently, you stopped saying you work for
them, did they wise up or was the whole thing a lie?

message
DAO for _ANY_ reason whatsover-- is not reccomended; it was not
included with Windows or Office for almost a decade.
DAO is a memory leak waiting to happen.


If your variables won't clean up after themselves; then move to
someone that will.
 
R

Roger Carlson

Well, you're wrong. DAO has been included in every version of Access since
Access 2.0. It was not SET as a reference in Access 2000 or 2002, but it
was certainly included. Whether it's called DAO in 2007 or not, is
immaterial and just an indication of the straws you are willing to grasp at
to prove your point.

--
--Roger Carlson
MS Access MVP
www.rogersaccesslibrary.com

message
I'm not so sure that is true.

It's not called DAO in 2007.
and it's not included - by default - in 2000 or 2002?

How many months was that between 2000 and the release of 2003?

How many more morsels of functionality can I do with ADO than you kids
can do with DAO?

How about _SHAPING_ the data?

Oh yah-- you guys don't know about that stuff.

DAO wasn't included with any version of MDAC from 2.6 upwards.
WIndows XP comes with MDAC 2.6.

I don't see-- what is wrong with my statement.

Everything that I said is 100% accurate.

_SORRY_.

I just won't be bullied into submission.

Take your JET or SHAREPOINT and _SHOVE_IT_.

-Aaron
 
A

a a r o n . k e m p f

Is it included 'by default'?

-Aaron



Well, you're wrong.  DAO has been included in every version of Access since
Access 2.0.  It was not SET as a reference in Access 2000 or 2002, but it
was certainly included.  Whether it's called DAO in 2007 or not, is
immaterial and just an indication of the straws you are willing to grasp at
to prove your point.

--
--Roger Carlson
   MS Access MVP
   www.rogersaccesslibrary.com

messageI'm not so sure that is true.

It's not called DAO in 2007.
and it's not included - by default - in 2000 or 2002?

How many months was that between 2000 and the release of 2003?

How many more morsels of functionality can I do with ADO than you kids
can do with DAO?

How about _SHAPING_ the data?

Oh yah-- you guys don't know about that stuff.

DAO wasn't included with any version of MDAC from 2.6 upwards.
WIndows XP comes with MDAC 2.6.

I don't see-- what is wrong with my statement.

Everything that I said is 100% accurate.

_SORRY_.

I just won't be bullied into submission.

Take your JET or SHAREPOINT and _SHOVE_IT_.

-Aaron






- Show quoted text -
 
A

a a r o n . k e m p f

re:
Whether it's called DAO in 2007 or not, is immaterial


I disagree. If the library should have been called DAO 6.0 and it's
called Microsoft Access Data Objects or something stupid like that..
is that _MY_ Fault??

Take your half asses DAO bullshit and shove it.

_ANY_ library that makes you 'clean up before the variables go out of
scope' is worthless at best.
_ANY_ library that makes you 'clean up before the variables go out of
scope' is worthless at best.
_ANY_ library that makes you 'clean up before the variables go out of
scope' is worthless at best.
_ANY_ library that makes you 'clean up before the variables go out of
scope' is worthless at best.
_ANY_ library that makes you 'clean up before the variables go out of
scope' is worthless at best.
_ANY_ library that makes you 'clean up before the variables go out of
scope' is worthless at best.
 
A

a a r o n . k e m p f

I'm sorry.

re:
I have used all versions and all had DAO. It
wasn't default for a version but seems to me, it is again

Can you explain that to me again-- word for word?

I mean.. Can I Just add a couple of words for you?

I have used all versions and all had DAO. It
wasn't default for a version but seems to me, it is again
_FOR_MY_DATABASE_TYPES_.

Sorry-- it is not included or default-- in Acess 2003 or Access 2007.
Blanket statements like that are not helpful, accurate or correct.

I am just here to clean up the misinformation that you fat old retards
give about DAO.

Again-- if your library makes you clean up after the variables-- THEN
FIND A NEW LIBRARY!

It actually is _NOT_ the default in Access 2007.
Or Access 2003 for that matter; you liars!

-Aaron
 
A

a a r o n . k e m p f

I'm sorry that was funny.

Someone I talked to last summer thought it was yelling!

-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