join with no related field

  • Thread starter Thread starter mcnews
  • Start date Start date
M

mcnews

i need to add a yes/no field to a linked table.
i would like to create a query that would join a table that contains
the yes/no field to the liked table.
i will use the yes/no field to allow the user to slect records for
later processing.
tia,
mcnewsxp
 
I never heard of doing what I think you said.
Did you say you want to join a table that has no relation at all to the
other? I have only heard of joining tables that have some data that is
common, even if only for a part of the data in the field. Maybe I
misunderstood you.

Then again you said "yes/no field to the liked table" but I do not
understand that. Please explain it a little bit more.
 
Then again you said "yes/no field to the liked table" but I do not
understand that. Please explain it a little bit more.
Click to expand...

my app allowed users to import data that is to used for creating
labels.
they can hand shoose the rows to be used in for the labels.
when all they wanted to do is import i added a boolean yes/no field to
the imprted table and used that field for user selection.

now they want to link to external tables.
so i added some code to add the boolean yes/no field to the linked
table.
it would be better to be able to add the boolean somehow within the
label app's data and not change the external data.
the users are ok with the way i have it, but i don't like it.
 
I can not help you.

mcnews said:
my app allowed users to import data that is to used for creating
labels.
they can hand shoose the rows to be used in for the labels.
when all they wanted to do is import i added a boolean yes/no field to
the imprted table and used that field for user selection.

now they want to link to external tables.
so i added some code to add the boolean yes/no field to the linked
table.
it would be better to be able to add the boolean somehow within the
label app's data and not change the external data.
the users are ok with the way i have it, but i don't like it.
Click to expand...
 
i need to add a yes/no field to a linked table.
i would like to create a query that would join a table that contains
the yes/no field to the liked table.
i will use the yes/no field to allow the user to slect records for
later processing.
tia,
mcnewsxp
Click to expand...

Your linked table MUST - no option! - have something to use as a link!

I'd suggest making its Primary Key a field of the same datatype as the
Primary Key of your main table (Long Integer if that's an autonumber);
include your yes/no field. You can then create a one to one join by
linking the two tables' primary keys, and you'll have the yes/no field
for the selection process.

If your second table consists only of a yes/no field then there is no
way, even in principle, to have Access know which "yes" in the second
table pertains to which record in the first.

John W. Vinson[MVP]
 
ok.
can i add a temp yes/no field via query?
Click to expand...

Not and have it editable, no. Queries are just a "view" of the data
stored in a Table; the data exists in the Table and ONLY in the table.

John W. Vinson[MVP]
 
KARL said:
I never heard of doing what I think you said.
Did you say you want to join a table that has no relation at all to the
other? I have only heard of joining tables that have some data that is
common, even if only for a part of the data in the field.
Click to expand...

See:

About joining tables or queries in a query (MDB)
http://office.microsoft.com/en-us/assistance/HP051885681033.aspx

"Cross-product or Cartesian product joins

"If tables in a query aren't joined to one another, either directly or
indirectly, Microsoft Access doesn't know which records are associated
with which, so it displays every combination of records between the two
tables. Therefore, if each table had 10 records in it, the query's
results will contain 100 records (10X10). This result set of every
possible combination is called a cross product or Cartesian product.
These queries might take a long time to run and ultimately might
produce less meaningful results."

Jamie.

--
 
KARL said:
I have only heard of joining tables that have some data that is
common, even if only for a part of the data in the field.
Click to expand...

Thinking of a usage scenario, I realized I tend to use a cross join
with an auxiliary table e.g. a one-column Sequence table of integers, a
Calendar table, etc.

For example, to parse out characters from a one-column table of input
strings:

SELECT T1.input_string, S1.seq,
MID$(T1.input_string, S1.seq, 1) AS char_parsed
FROM InputStrings AS T1, [Sequence] AS S1
WHERE S1.seq BETWEEN 1 AND LEN(input_string);

One table holds only integers and the other only text but the ability
to cross join is extremely useful.

Jamie.

--
 
Back
Top