parameter

[al9315]

Typed question earlier - cannot find it on here ???????
Query - Record Collection - e.g. "We wish you a Merry Xmas" - Parameter
Query - type in e.g. Merry Xmas - search ALL track fields (in my case - 24
fields) in ALL records for any instance of tracks with "Merry Xmas" in ?

 

[Chris2]

Typed question earlier - cannot find it on here ???????
Query - Record Collection - e.g. "We wish you a Merry Xmas" - Parameter
Query - type in e.g. Merry Xmas - search ALL track fields (in my case - 24
fields) in ALL records for any instance of tracks with "Merry Xmas"

in ?

If I understand correctly:

SELECT T1.Track
FROM YourTable AS T1
WHERE T1.Track LIKE "*Merry Xmas*";


Sincerely,

Chris O.

 

[Marshall Barton]

Typed question earlier - cannot find it on here ???????
Query - Record Collection - e.g. "We wish you a Merry Xmas" - Parameter
Query - type in e.g. Merry Xmas - search ALL track fields (in my case - 24
fields) in ALL records for any instance of tracks with "Merry Xmas" in ?

24 track fields???

Searching such an unnormalized structure will be a nightmare
and might even exceed some limits.

Before you get too much further down this road, take the
time now to create a more relational table structure. You
should have a separate table for the tracks that has a field
for the title along with a field with the foreign key to the
records table.

This kind of structure is trivial to search since there is
only one field to search.

 

[al9315]

I understand exactly what you say, I did start off with the tracks in a
seperate table, but could not keep all integrity going with seperate track
table for some reason. I am unfortunately, trying to learn Acces on my own ?!
The data was originally on Dataease, but with Windows XP - DOS programmes
are gone !!
I do not have the ability to give up, so will persevere, what you said makes
profound sense to me !!!
Thanks again
Al

 

[Chris2]

case - 24

24 fields? Oops. Nevermind.

Write a VBA function that accepts a paramets of "AlbumID", opens a
recordset, looks up the row based on the Album ID, checks each of the
24 columns, and returns whatever you need it to when it finds what
it's looking for.


Sincerely,

Chris O.

 

[John Vinson]

I understand exactly what you say, I did start off with the tracks in a
seperate table, but could not keep all integrity going with seperate track
table for some reason. I am unfortunately, trying to learn Acces on my own ?!
The data was originally on Dataease, but with Windows XP - DOS programmes
are gone !!

You'll find that Access is considerably more powerful and flexible.

You may want to have two tables (at least):

CDS
CD_ID << an autonumber or other unique identifier for a recording
Title
<other info about the CD as an object>

Tracks
CD_ID << link to the CDS table
TrackNo << number 1-24 (or 1-85, or 1-3, or whatever)
Title
<other info about this track>

If you do data entry on a Form based on CDS, with a Subform based on
Tracks, you'll maintain the integrity.

John W. Vinson[MVP]