 | |
#1
 
| |||
| |||
|
Double Query -
03-25-2008
, 09:46 AM
#2
| |||
| |||
|
|
On an occasion or two, when I did Open Query I got two Query bars, both just alike. What causes this, and what's the best resolution? (This is on my mailing label database, Paradox 8, Windows 98SE.) |
A query can involve more than one table at a time. For example, a query
about "Orders" might also involve a table of "Customers." And if you look
closely, you'll notice that the two tables are "linked" in some way using
so-called "example elements." For instance, the query that I'm describing
would most-likely link the two tables by, say, "CustID."
The reason why you might want to do that should, actually, be pretty
obvious: you want to get information about each customer. The "Orders"
table does not repeat the information about the customer: it only contains
the "CustID." So the query will retrieve "whatever you want to know about
this customer" from the "Customers" table. This is a key concept of
a "relational" database.
----
ChimneySweep(R): Fast(!) table repair at a click of the mouse!
http://www.sundialservices.com
#3
| |||
| |||
|
|
On an occasion or two, when I did Open Query I got two Query bars, both just alike. What causes this, and what's the best resolution? (This is on my mailing label database, Paradox 8, Windows 98SE.) |
A query can involve more than one table at a time. For example, a query
about "Orders" might also involve a table of "Customers." And if you look
closely, you'll notice that the two tables are "linked" in some way using
so-called "example elements." For instance, the query that I'm describing
would most-likely link the two tables by, say, "CustID."
The reason why you might want to do that should, actually, be pretty
obvious: you want to get information about each customer. The "Orders"
table does not repeat the information about the customer: it only contains
the "CustID." So the query will retrieve "whatever you want to know about
this customer" from the "Customers" table. This is a key concept of
a "relational" database.
----
ChimneySweep(R): Fast(!) table repair at a click of the mouse!
http://www.sundialservices.com
#4
| |||
| |||
|
|
On an occasion or two, when I did Open Query I got two Query bars, both just alike. What causes this, and what's the best resolution? (This is on my mailing label database, Paradox 8, Windows 98SE.) |
A query can involve more than one table at a time. For example, a query
about "Orders" might also involve a table of "Customers." And if you look
closely, you'll notice that the two tables are "linked" in some way using
so-called "example elements." For instance, the query that I'm describing
would most-likely link the two tables by, say, "CustID."
The reason why you might want to do that should, actually, be pretty
obvious: you want to get information about each customer. The "Orders"
table does not repeat the information about the customer: it only contains
the "CustID." So the query will retrieve "whatever you want to know about
this customer" from the "Customers" table. This is a key concept of
a "relational" database.
----
ChimneySweep(R): Fast(!) table repair at a click of the mouse!
http://www.sundialservices.com
#5
| |||
| |||
|
|
On an occasion or two, when I did Open Query I got two Query bars, both just alike. What causes this, and what's the best resolution? (This is on my mailing label database, Paradox 8, Windows 98SE.) |
A query can involve more than one table at a time. For example, a query
about "Orders" might also involve a table of "Customers." And if you look
closely, you'll notice that the two tables are "linked" in some way using
so-called "example elements." For instance, the query that I'm describing
would most-likely link the two tables by, say, "CustID."
The reason why you might want to do that should, actually, be pretty
obvious: you want to get information about each customer. The "Orders"
table does not repeat the information about the customer: it only contains
the "CustID." So the query will retrieve "whatever you want to know about
this customer" from the "Customers" table. This is a key concept of
a "relational" database.
----
ChimneySweep(R): Fast(!) table repair at a click of the mouse!
http://www.sundialservices.com
#6
| |||
| |||
|
|
On an occasion or two, when I did Open Query I got two Query bars, both just alike. What causes this, and what's the best resolution? (This is on my mailing label database, Paradox 8, Windows 98SE.) |
A query can involve more than one table at a time. For example, a query
about "Orders" might also involve a table of "Customers." And if you look
closely, you'll notice that the two tables are "linked" in some way using
so-called "example elements." For instance, the query that I'm describing
would most-likely link the two tables by, say, "CustID."
The reason why you might want to do that should, actually, be pretty
obvious: you want to get information about each customer. The "Orders"
table does not repeat the information about the customer: it only contains
the "CustID." So the query will retrieve "whatever you want to know about
this customer" from the "Customers" table. This is a key concept of
a "relational" database.
----
ChimneySweep(R): Fast(!) table repair at a click of the mouse!
http://www.sundialservices.com
#7
| |||
| |||
|
|
On an occasion or two, when I did Open Query I got two Query bars, both just alike. What causes this, and what's the best resolution? (This is on my mailing label database, Paradox 8, Windows 98SE.) |
A query can involve more than one table at a time. For example, a query
about "Orders" might also involve a table of "Customers." And if you look
closely, you'll notice that the two tables are "linked" in some way using
so-called "example elements." For instance, the query that I'm describing
would most-likely link the two tables by, say, "CustID."
The reason why you might want to do that should, actually, be pretty
obvious: you want to get information about each customer. The "Orders"
table does not repeat the information about the customer: it only contains
the "CustID." So the query will retrieve "whatever you want to know about
this customer" from the "Customers" table. This is a key concept of
a "relational" database.
----
ChimneySweep(R): Fast(!) table repair at a click of the mouse!
http://www.sundialservices.com
#8
| |||
| |||
|
|
On an occasion or two, when I did Open Query I got two Query bars, both just alike. What causes this, and what's the best resolution? (This is on my mailing label database, Paradox 8, Windows 98SE.) |
A query can involve more than one table at a time. For example, a query
about "Orders" might also involve a table of "Customers." And if you look
closely, you'll notice that the two tables are "linked" in some way using
so-called "example elements." For instance, the query that I'm describing
would most-likely link the two tables by, say, "CustID."
The reason why you might want to do that should, actually, be pretty
obvious: you want to get information about each customer. The "Orders"
table does not repeat the information about the customer: it only contains
the "CustID." So the query will retrieve "whatever you want to know about
this customer" from the "Customers" table. This is a key concept of
a "relational" database.
----
ChimneySweep(R): Fast(!) table repair at a click of the mouse!
http://www.sundialservices.com
#9
| |||
| |||
|
#10
| |||
| |||
|
 |
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.