Yes, QryRpt and QrySRpt. Another thing this all does is group the queries in
the databse window by use. All the queries that are the basis of a report
are together because they all begin with QryRpt. Same thing for QrySRpt,
QryFrm, QryPFrm and QrySFrm. So if you have a lot of queries and you are
looking for a certain one in the database window, you can immediately go to
the appropriate group and look there. Another benefit to using this naming
convention is that in code you can immediately tell if an object is a table
or query. Lots of times in databases you see an object named Customers.
There's no way to tell if it is a table or query. Obviously the naming
convention needs to be applied to forms (Frm, PFrm and SFrm) and reports
(Rpt, SRpt) too. We were going to get to all this in the tutoring sessions!
Do you then do that for reports. It sounds quite helpful.
It's just my naming convention but it helps a lot when looking at all the
queries in the database window whem trying to find the one you want or
identifying what a query is used for. Queries for forms begin with QryFrm,
QryPFrm or QrySFrm. Right away you can see that QrySpeciality is not the
basis for any form.
Steve
Sorry...
Would you name the query QryFrmPhysician or just QryPhysician and if it's
QryFrm, is that to identify that it is a query made for a form?
Thanks,
Linda
Name of the query based on TblPhysician. The main form, named FrmPhysician,
is then based on this query.
You will also see QrySpeciality. It is the name of a query based on
TblSpeciality. It is used as the rowsource for the combobox in the subform.
Steve
Steve,
What is a QryFrmPhysician?
Thanks,
Lina
Hi Linda,
Still working on the database??
TblPhysician
PhysicianID
FName
LName
etc
TblSpeciality
SpecialityID
Speciality
TblPhysicianSpeciality
PHysicianSpecialityID
PhysicianID
SpecialityID
Create the following relationships:
1. PhysicianID in TblPhysician to PhysicianID in TblPhysicianSpeciality
2. SpecialityID in TblSpeciality to SpecialityID in TblPhysicianSpeciality
Create QryFrmPhysician based on TblPhysician. Make PhysicianID the first
field and in the second field, concatenate FName and LName. In the third
include LName. Sort ascending on LName.
Create QrySpeciality based on TblSpeciality. Sort ascending on Speciality.
Create a mainform/subform. Base the main form on QryFrmPhysician and base
the subform on TblPhysicianSpeciality. Set the LinkMaster/Linkchild
properties to PhysicianID. In the subform, change the SpecialityID textbox
to a combobox. For the combobox, set the rowsource to QrySpeciality, bound
column to 1, column count to 2 and column widths to 0;1.5.
You can now enter the physicians and their specialities with the
form/subform.
Steve
PC Datasheet
Hi Guys,
I want a physician look up list in my database. I have another flat
database with physician FName, LName, and Specialty all in one table. My
database has a Specialty table and a Physician Name table. Is there anyway
to make a query with the physicians table to make a list that can go into my
database and have a relationship between the physicianID and Specialty. The
only way I know to do it would be to import the physician names and then
type in the specialty...or come to think of it, I don't know how I would do
that either. I need a suggestion on what I should do to avoid typing 1245
physicians into my database.
Thanks,
Linda
