Selasa, 31 Mei 2011

Re: [MS_AccessPros] Re: Help with relationships

 

Thanks.

________________________________
From: John Viescas <john@viescas.com>
To: MS_Access_Professionals@yahoogroups.com
Sent: Tuesday, May 31, 2011 11:58 AM
Subject: RE: [MS_AccessPros] Re: Help with relationships

 
Joe-

You could compact / zip, and post it to the group Assistance Needed folder.

John Viescas, author
Microsoft Office Access 2010 Inside Out
Microsoft Office Access 2007 Inside Out
Building Microsoft Access Applications
Microsoft Office Access 2003 Inside Out
SQL Queries for Mere Mortals
http://www.viescas.com/
(Paris, France)

-----Original Message-----
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Joe HErnandez
Sent: Tuesday, May 31, 2011 5:48 PM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] Re: Help with relationships

John;

I made the changes you suggested to the db.
Do you want me to re-send it to you so that you can look it over?

Joe

________________________________
From: John Viescas <john@viescas.com>
To: MS_Access_Professionals@yahoogroups.com
Sent: Tuesday, May 31, 2011 12:58 AM
Subject: RE: [MS_AccessPros] Re: Help with relationships

Joe-

Wow! Freddy & Soraya must be pretty special people to have fields named after them in the database. <s> What happens if Soraya finds a better job and moves on? You'll have to redesign your table - and that's not a good idea. I have no idea how you plan to enforce security, but a Users table should normally look like:

tblUsers:
UserID (PKey)
UserName
UserPswd
UserAuth

Then you put rows in for Soraya and Freddie and set their authorization level. If another person comes on board, you just add a row. If someone leaves, you delete the row. No changes to the design necessary.

As for tracking patients and results, it might look something like:

tblPatients:
PatientID:
PatientName
.. other relevant fields such as address, phone number, referring doctor, etc.

tblPatientAppointments:
AppointmentID
PatientID
AppointmentDate
... etc.

tblPatientAppointmentTests:
TestID
AppointmentID
TestType
TestResult

If a particular test can have more than one result, then instead of putting TestResult in that table, you'll need:

tblPatientApptTestResults:
ResultID
TestID
Result

The database will have one row for each patient, one row for each appointment, one row for each test performed during an appointment, and one row for each result for each test. To track "next" appointment, you might need a FollowUpDate in tblPatientAppointments, but you'll create a new row in tblPatientAppointments for the follow-up.

John Viescas, author
Microsoft Office Access 2010 Inside Out
Microsoft Office Access 2007 Inside Out
Building Microsoft Access Applications
Microsoft Office Access 2003 Inside Out
SQL Queries for Mere Mortals
http://www.viescas.com/
(Paris, France)

-----Original Message-----
From: MS_Access_Professionals@yahoogroups.com [mailto:MS_Access_Professionals@yahoogroups.com] On Behalf Of Joe HErnandez
Sent: Tuesday, May 31, 2011 12:57 AM
To: MS_Access_Professionals@yahoogroups.com
Subject: Re: [MS_AccessPros] Re: Help with relationships

John; thanks for getting back to me.

The purpose of this db is to track:
· Patient/clients'
visits (dates)
· When and
if they returned for results ,after each test (dates)
· When is
their follow- up appts .
Please keep in mind that these patients (most of them) will
return multiple times for re- testing and after each test they in turn will
return for results. Hence, the
repetition.

The two people who will be doing the tests (testers) are Soraya and Freddie.

________________________________
From: johnvmvp <john@viescas.com>
To: MS_Access_Professionals@yahoogroups.com
Sent: Monday, May 30, 2011 11:43 AM
Subject: [MS_AccessPros] Re: Help with relationships

Joe-

I have your database, but the purpose of the database is not clear.

You have a bad problem with both the Tests and Results tables. In the Tests tables, fields like TestDt1, TestDt2 and 2ndTestAppt_DT and 3rdTestAppt_DT are repeating groups. Ditto Rslt1, Rslt2, Rslt3, etc. in Results.

The fields in L_AccessLevel make no sense. What are the Soraya and Freddie fields?

John Viescas, author
Microsoft Office Access 2010 Inside Out
Microsoft Office Access 2007 Inside Out
Building Microsoft Access Applications
Microsoft Office Access 2003 Inside Out
SQL Queries for Mere Mortals
http://www.viescas.com/
(Paris, France)

--- In MS_Access_Professionals@yahoogroups.com, "JoeH" <jomahe0143@...> wrote:
>
> I am trying to build a database for my daughter. So far I have identified the tables and built some of the forms I feel I need.
> I would like someone to help me connect the relationships and if at all possible provide any feedback deemed useful.
>
> If you need to see what I have done up to this point, please let me know how to attach the file.
>
> In advance I thank you
> sincerely
> Joe Hernandez
>
> P.S. I am using Access 2010 and my OS is Win 7.
>

[Non-text portions of this message have been removed]

------------------------------------

Yahoo! Groups Links

[Non-text portions of this message have been removed]

------------------------------------

Yahoo! Groups Links

[Non-text portions of this message have been removed]

__._,_.___
Recent Activity:
.

__,_._,___

Tidak ada komentar:

Posting Komentar