这叫什么？ [英] what is it called?
问题描述
大家好，
我不记得它叫什么，但我知道它确实有一个名字我
以为我记得它是一个'级联事件''，但我不认为
这就是所谓的。
senario：
您的主键有重复，因此当您创建一个查询，将标题中的
主键加入详细信息中的forgien键时，您将获得
bogus结果，你得到每个标题记录的一组细节。
谢谢
bobh。
bobh写道：
大家好，
我不记得了它叫什么，但我知道它有一个名字我
以为我记得它是一个'级联事件''但我不认为
'这才是真正的名字。
这可能被称为错误。
>
senario：
您的主键有重复，因此当您创建一个加入的查询时
你获得的详细信息中forgien键的标题中的主键
bogus结果，你得到每个标题记录的一组细节。
主键如何重复...除非你把它设置为
作为主键并允许重复？但是它不会是一个主键......一个使该行唯一的键。
>
谢谢
bobh。
9月5日12:04 pm，Salad< o ... @ vinegar.comwrote：
bobh写道：
Hi All，
我不记得它叫什么，但我知道它确实有一个名字我
以为我记得它是一个'级联事件但我不认为
这就是它真正被称为的东西。
这可能被称为错误。
senario：
your主键有重复，所以当你创建一个查询，将标题中的
主键连接到详细信息中的forgien键时，你得到一个b / b
bogus结果，你得到一个集合每个标题记录的详细信息。
主键如何重复...除非你把它设置为
作为主键并允许重复？但是那时它不会是一个主键......一个使该行唯一的键。
谢谢
bobh.-隐藏引用的文字 -
- 显示引用的文字 -
我同意，这是一个错误或糟糕的设计:)但在处理时，我想b $ b猜我必须称他们为新手构建的应用程序和/或旧主机
数据下载到存在问题的访问表。我遇到很多很多情况，我必须要处理的数据远远不是完美甚至标准化的。
bobh。
bobh写道：
9月5日下午12:04，Salad< o ... @ vinegar.comwrote：
>> bobh写道：
> >>大家好，
>>>我不记得它叫什么，但我知道它确实有一个名字我
以为我记得它是一个'级联事件''但我不认为这就是它真正的名字。
这可能被称为错误。
>>> senario：
您的主键有重复，因此当您创建一个查询，将标题中的
主键连接到详细信息中的forgien键时，您将得到一个伪造结果的详细信息，您将获得每个标题记录的一组详细信息。
主键如何重复...除非你把它设置为主键并允许重复？但是它不会成为主键......这一行使该行独一无二。
>>>谢谢
bobh.-隐藏引用的文字 -
- 显示引用的文字 -
我同意，这是一个错误或糟糕的设计:)但在处理时，我猜b $ b猜我必须称他们为新手构建的应用程序和/或旧主机
数据下载以访问存在问题的表。我遇到很多很多情况，我必须要处理的数据远远不是完美甚至标准化的。
bobh。
好吧，我们还没有yoru问题的定义。
字也不是错误。提供任何方法来纠正它。我想你要去创建一个像autonumber这样的字段来创建一个真正的主要元素b $ b键。
。祝你好运。
Hi All,
I can''t remember what it is called but I know it did have a name I
thought I remembered it as a ''cascading event'' but I don''t think
that''s what it really is called.
senario:
your primary key has dups so when you create a query which joins the
primary key in the header to the forgien key in the detail you get
bogus results, you get a set of detail of each header record.
thanks
bobh.
bobh wrote:Hi All,
I can''t remember what it is called but I know it did have a name I
thought I remembered it as a ''cascading event'' but I don''t think
that''s what it really is called.It might be called a mistake.
>
senario:
your primary key has dups so when you create a query which joins the
primary key in the header to the forgien key in the detail you get
bogus results, you get a set of detail of each header record.How can a primary key have duplicates...unless you set it up that way as
to being a primary key and allowing duplicates? But then it would not
be a primary key...a key that makes that row unique.
>
thanks
bobh.
On Sep 5, 12:04 pm, Salad <o...@vinegar.comwrote:bobh wrote:Hi All,
I can''t remember what it is called but I know it did have a name I
thought I remembered it as a ''cascading event'' but I don''t think
that''s what it really is called.
It might be called a mistake.
senario:
your primary key has dups so when you create a query which joins the
primary key in the header to the forgien key in the detail you get
bogus results, you get a set of detail of each header record.
How can a primary key have duplicates...unless you set it up that way as
to being a primary key and allowing duplicates? But then it would not
be a primary key...a key that makes that row unique.
thanks
bobh.- Hide quoted text -
- Show quoted text -I agree, it''s a mistake or bad design :) but when dealing with, I
guess I would have to call them novice built apps and/or old mainframe
data downloaded to access tables that issue exists. I have run into
many, many situations where the data I have to deal with is far from
perfect or even normalized.
bobh.
bobh wrote:On Sep 5, 12:04 pm, Salad <o...@vinegar.comwrote:
>>bobh wrote:
>>>Hi All,
>>>I can''t remember what it is called but I know it did have a name I
thought I remembered it as a ''cascading event'' but I don''t think
that''s what it really is called.
It might be called a mistake.
>>>senario:
your primary key has dups so when you create a query which joins the
primary key in the header to the forgien key in the detail you get
bogus results, you get a set of detail of each header record.
How can a primary key have duplicates...unless you set it up that way as
to being a primary key and allowing duplicates? But then it would not
be a primary key...a key that makes that row unique.
>>>thanks
bobh.- Hide quoted text -
- Show quoted text -
I agree, it''s a mistake or bad design :) but when dealing with, I
guess I would have to call them novice built apps and/or old mainframe
data downloaded to access tables that issue exists. I have run into
many, many situations where the data I have to deal with is far from
perfect or even normalized.
bobh.
Well, we don''t have the definition yet of yoru problem. Nor does the
word "mistake" provide any method to correct it. I guess you are going
to need to create a field, like an autonumber, to create a true primary
key. Best of luck.
这篇关于这叫什么？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
