If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > General > Database Concepts & Design > User interface

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 04-19-07, 12:36
bjboyce68 bjboyce68 is offline
Registered User
 
Join Date: Apr 2007
Posts: 7
User interface

I am working on a Project for a Data management class and need to provide my MySql information in some sort of user interface for the professor...any suggestions?
Reply With Quote
  #2 (permalink)  
Old 04-19-07, 12:43
pootle flump pootle flump is offline
King of Understatement
 
Join Date: Feb 2004
Location: One Flump in One Place
Posts: 14,905
Well..... the starting point would likely seem to be whatever information the professor asked for.

I'm afraid your question is far too vague. What do you want to show? How do you want to show it? What platform do you want to use?
__________________
Testimonial:
Quote:
pootle flump
ur codings are working excelent.
Reply With Quote
  #3 (permalink)  
Old 04-19-07, 12:46
bjboyce68 bjboyce68 is offline
Registered User
 
Join Date: Apr 2007
Posts: 7
well it is a database in MySql and she wants some sort of GUI I guess..
Reply With Quote
  #4 (permalink)  
Old 04-19-07, 12:49
pootle flump pootle flump is offline
King of Understatement
 
Join Date: Feb 2004
Location: One Flump in One Place
Posts: 14,905
Lol - what sort of grade are you aiming for?

Seriously - your profile says you are 38 - you must have some experience in... well something. Surely you know you can't really achieve a goal without having some inkling what that goal is? In the programming and database design world you have to extend that concept a long, long way and come up with something really specific. There is no "some sort" of anything when it comes to specifying a technical system.
__________________
Testimonial:
Quote:
pootle flump
ur codings are working excelent.
Reply With Quote
  #5 (permalink)  
Old 04-19-07, 12:52
bjboyce68 bjboyce68 is offline
Registered User
 
Join Date: Apr 2007
Posts: 7
THat's just it...she is too vague on what she wants. Yes I am 38...you are funny...
Reply With Quote
  #6 (permalink)  
Old 04-19-07, 12:55
pootle flump pootle flump is offline
King of Understatement
 
Join Date: Feb 2004
Location: One Flump in One Place
Posts: 14,905
Quote:
Originally Posted by bjboyce68
THat's just it...she is too vague on what she wants.
Then you either need to decide the spec yourself or get her to spec it. We can't do that for you.

Quote:
Originally Posted by bjboyce68
you are funny...
Indeed I am.
__________________
Testimonial:
Quote:
pootle flump
ur codings are working excelent.
Reply With Quote
  #7 (permalink)  
Old 04-19-07, 12:59
bjboyce68 bjboyce68 is offline
Registered User
 
Join Date: Apr 2007
Posts: 7
I am definitely not asking for it to be done...I need to learn that myself...I will get some more info...thanks for your help
Reply With Quote
  #8 (permalink)  
Old 04-19-07, 13:11
r937 r937 is offline
SQL Consultant
 
Join Date: Apr 2002
Location: Toronto, Canada
Posts: 19,524
b j boyce -- do a SHOW CREATE TABLE for all your tables, and post the results here, and i can help you

__________________
r937.com | rudy.ca
please visit Simply SQL and buy my book
Reply With Quote
  #9 (permalink)  
Old 04-19-07, 13:51
bjboyce68 bjboyce68 is offline
Registered User
 
Join Date: Apr 2007
Posts: 7
Quote:
Originally Posted by r937
b j boyce -- do a SHOW CREATE TABLE for all your tables, and post the results here, and i can help you

I can do that:

Appointment table:

| appointment | CREATE TABLE `appointment` (
`pat_id` char(8) NOT NULL default '',
`appt_date` date NOT NULL default '0000-00-00',
`appt_time` time default NULL,
`prov_id` char(6) default NULL,
`treat_code` varchar(8) default NULL,
PRIMARY KEY (`pat_id`,`appt_date`),
KEY `prov_id` (`prov_id`),
CONSTRAINT `appointment_ibfk_1` FOREIGN KEY (`pat_id`) REFERENCES `patient` (`
pat_id`) ON UPDATE CASCADE,
CONSTRAINT `appointment_ibfk_2` FOREIGN KEY (`prov_id`) REFERENCES `provider`
(`prov_id`) ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |

Bill Table:

| bill | CREATE TABLE `bill` (
`invoice_num` char(6) NOT NULL default '',
`invoice_date` date default NULL,
`bill_payer` varchar(30) default NULL,
`amt_due` decimal(9,2) default NULL,
PRIMARY KEY (`invoice_num`),
KEY `bill_payer` (`bill_payer`),
CONSTRAINT `bill_ibfk_1` FOREIGN KEY (`bill_payer`) REFERENCES `payer` (`bill_
payer`) ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |

Cost table:
| cost | CREATE TABLE `cost` (
`treatment` varchar(20) NOT NULL default '',
`price` decimal(9,2) default NULL,
PRIMARY KEY (`treatment`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |

Patient table:
| patient | CREATE TABLE `patient` (
`pat_id` char(8) NOT NULL default '',
`pat_fname` varchar(15) default NULL,
`pat_lname` varchar(15) default NULL,
`pat_gender` char(1) default NULL,
`pat_dob` date default NULL,
`pat_ssn` char(11) default NULL,
`pat_phone` char(12) default NULL,
`pat_street` varchar(30) default NULL,
`pat_city` varchar(25) default NULL,
`pat_state` char(2) default NULL,
`pat_zip` char(5) default NULL,
`bill_payer` varchar(30) default NULL,
PRIMARY KEY (`pat_id`),
KEY `bill_payer` (`bill_payer`),
CONSTRAINT `patient_ibfk_1` FOREIGN KEY (`bill_payer`) REFERENCES `payer` (`bi
ll_payer`) ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |

Patient_record table:
| patient_record | CREATE TABLE `patient_record` (
`pat_id` char(8) NOT NULL default '',
`appt_date` date NOT NULL default '0000-00-00',
`treatment` varchar(20) NOT NULL default '',
`prov_id` char(6) default NULL,
PRIMARY KEY (`pat_id`,`appt_date`,`treatment`),
KEY `treatment` (`treatment`),
KEY `prov_id` (`prov_id`),
CONSTRAINT `patient_record_ibfk_1` FOREIGN KEY (`pat_id`, `appt_date`) REFEREN
CES `appointment` (`pat_id`, `appt_date`) ON UPDATE CASCADE,
CONSTRAINT `patient_record_ibfk_2` FOREIGN KEY (`treatment`) REFERENCES `cost`
(`treatment`) ON UPDATE CASCADE,
CONSTRAINT `patient_record_ibfk_3` FOREIGN KEY (`prov_id`) REFERENCES `provide
r` (`prov_id`) ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |

Payer table:
| payer | CREATE TABLE `payer` (
`bill_payer` varchar(30) NOT NULL default '',
`payer_phone` char(12) default NULL,
`payer_street` varchar(30) default NULL,
`payer_city` varchar(25) default NULL,
`payer_state` char(2) default NULL,
`payer_zip` char(5) default NULL,
`relation_to_patient` varchar(15) default NULL,
`amt_owed` decimal(9,2) default NULL,
PRIMARY KEY (`bill_payer`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |

Payment table:
| payment | CREATE TABLE `payment` (
`bill_payer` varchar(30) NOT NULL default '',
`payment_date` date NOT NULL default '0000-00-00',
`source` varchar(15) default NULL,
`amt` decimal(9,2) default NULL,
PRIMARY KEY (`bill_payer`,`payment_date`),
CONSTRAINT `payment_ibfk_1` FOREIGN KEY (`bill_payer`) REFERENCES `payer` (`bi
ll_payer`) ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |

Provider table:
| provider | CREATE TABLE `provider` (
`prov_id` char(6) NOT NULL default '',
`prov_name` varchar(30) default NULL,
`prov_phone` char(12) default NULL,
`treat_code` varchar(8) default NULL,
PRIMARY KEY (`prov_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |

Treatment_given table:
| treatment_given | CREATE TABLE `treatment_given` (
`pat_id` char(8) NOT NULL default '',
`treatment` varchar(20) NOT NULL default '',
`comments` varchar(30) default NULL,
PRIMARY KEY (`pat_id`,`treatment`),
KEY `treatment` (`treatment`),
CONSTRAINT `treatment_given_ibfk_1` FOREIGN KEY (`pat_id`) REFERENCES `patient
` (`pat_id`) ON UPDATE CASCADE,
CONSTRAINT `treatment_given_ibfk_2` FOREIGN KEY (`treatment`) REFERENCES `cost
` (`treatment`) ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |

Treatment_type table:
| treatment_type | CREATE TABLE `treatment_type` (
`pat_id` char(8) NOT NULL default '',
`treat_code` varchar(8) NOT NULL default '',
`treat_desc` varchar(30) default NULL,
PRIMARY KEY (`pat_id`,`treat_code`),
CONSTRAINT `treatment_type_ibfk_1` FOREIGN KEY (`pat_id`) REFERENCES `patient`
(`pat_id`) ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=latin1 |
Reply With Quote
  #10 (permalink)  
Old 04-19-07, 14:35
blindman blindman is offline
World Class Flame Warrior
 
Join Date: Jun 2003
Location: Ohio
Posts: 11,726
Quote:
Originally Posted by bjboyce68
I am working on a Project for a Data management class and need to provide my MySql information in some sort of user interface for the professor...any suggestions?
Use MS Access or Excel, depending upon the complexity of the schema.
__________________
If it's not practically useful, then it's practically useless.

blindman
www.chess.com: "sqlblindman"
Reply With Quote
  #11 (permalink)  
Old 04-19-07, 14:40
bjboyce68 bjboyce68 is offline
Registered User
 
Join Date: Apr 2007
Posts: 7
Quote:
Originally Posted by blindman
Use MS Access or Excel, depending upon the complexity of the schema.
I don't have Access but I do have Excel
Reply With Quote
  #12 (permalink)  
Old 04-19-07, 15:38
blindman blindman is offline
World Class Flame Warrior
 
Join Date: Jun 2003
Location: Ohio
Posts: 11,726
How functional does the user interface have to be? You could just link to the tables through Excel.
__________________
If it's not practically useful, then it's practically useless.

blindman
www.chess.com: "sqlblindman"
Reply With Quote
  #13 (permalink)  
Old 04-20-07, 09:48
urquel urquel is offline
Registered User
 
Join Date: Aug 2004
Posts: 330
How about suggesting a command prompt interface and let the end user type their commands and sql statements manually. This will allow maxmum versatility and allow the end user to specify exactly what they want.
Reply With Quote
  #14 (permalink)  
Old 04-22-07, 20:49
sco08y sco08y is offline
Registered User
 
Join Date: Oct 2002
Location: Baghdad, Iraq
Posts: 697
Quote:
Originally Posted by urquel
How about suggesting a command prompt interface and let the end user type their commands and sql statements manually. This will allow maxmum versatility and allow the end user to specify exactly what they want.
Yeah, how about something like the old Zork games?

Code:
You are in a maze of tables. Relations and constraints branch off
in all directions.

> Go to Patients.

You trudge through the dusty medical records for what seems like 
hours. Finally you decide that you are getting nowhere and give up.

> Look.

It is dark. You are likely to be eaten by a grue.
Reply With Quote
  #15 (permalink)  
Old 04-22-07, 23:03
blindman blindman is offline
World Class Flame Warrior
 
Join Date: Jun 2003
Location: Ohio
Posts: 11,726
That's hilarious. Wish I'd thought of it!
Damn grue....
__________________
If it's not practically useful, then it's practically useless.

blindman
www.chess.com: "sqlblindman"
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On