S
snicker7
Guest
Before I explain the problem, let me explain the goal here.
Ive designed a database for an apartment cleaning company. Currently there are three tables that apply directly to a single apartment.
The tables are this:
tblApartments:
Aptcode: consists of a two to four letter apartment complex code
AptNumber: the room number of the apartment, which is not strictly a numerical field
WhoWalked: person that last walked the apartment
DateWalked: Obviously the date the above person walked it
Notes: a memo field.
tblAptCodes:
Aptcode: directly related to the above field.
Aptname: the corresponding name to the two to four letter apartment complex code.
then address and phone fields for the complexes
tblDates:
datecleaned: dates the apartment was cleaned
whocleaned: who cleaned it on that date
notes: duh
Each apartment is linked to the apartment complex codes table, and then each apartment has dates in the dates table when it was cleaned. The dates table is linked by the AptID field in tblApartments.
I used Parker's simple search in the sample DBs section to do a base search of a combination of these three tables into a listbox. The list box contains these values:
tblAptCodes.AptCode, tblAptCodes.Name, tblApartments.AptNumber, tblApartments.WhoWalked, tblDates.DateCleaned, tblDates.WhoCleaned
The query is rather complicated, so i have multiple listings for each apartment, but the listings each have different dates. Now to the actual point.
Currently, with parkers simple search, I can only reference one column of data at a time. What I mean by this is if I have an apartment with code CC and room number 1234, If I type "cc 1234" into my query box, I get no returns.
I need a way for this simple search to be able to reference many fields with independent data, as separated by a space. So if i want to find apartments in the AMI complex cleaned by Harry, i type in "ami harry" and i get the records. This input must stay a single field. I hope that I have explained myself well enough.
Ive designed a database for an apartment cleaning company. Currently there are three tables that apply directly to a single apartment.
The tables are this:
tblApartments:
Aptcode: consists of a two to four letter apartment complex code
AptNumber: the room number of the apartment, which is not strictly a numerical field
WhoWalked: person that last walked the apartment
DateWalked: Obviously the date the above person walked it
Notes: a memo field.
tblAptCodes:
Aptcode: directly related to the above field.
Aptname: the corresponding name to the two to four letter apartment complex code.
then address and phone fields for the complexes
tblDates:
datecleaned: dates the apartment was cleaned
whocleaned: who cleaned it on that date
notes: duh
Each apartment is linked to the apartment complex codes table, and then each apartment has dates in the dates table when it was cleaned. The dates table is linked by the AptID field in tblApartments.
I used Parker's simple search in the sample DBs section to do a base search of a combination of these three tables into a listbox. The list box contains these values:
tblAptCodes.AptCode, tblAptCodes.Name, tblApartments.AptNumber, tblApartments.WhoWalked, tblDates.DateCleaned, tblDates.WhoCleaned
The query is rather complicated, so i have multiple listings for each apartment, but the listings each have different dates. Now to the actual point.
Currently, with parkers simple search, I can only reference one column of data at a time. What I mean by this is if I have an apartment with code CC and room number 1234, If I type "cc 1234" into my query box, I get no returns.
I need a way for this simple search to be able to reference many fields with independent data, as separated by a space. So if i want to find apartments in the AMI complex cleaned by Harry, i type in "ami harry" and i get the records. This input must stay a single field. I hope that I have explained myself well enough.