Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
jologz
Starting Member
1 Post |
 Posted - 2009-11-23 : 20:04:51
|
| Hi everyone,I actually need advice on how to attact this problem. I'll give an example so that it will be easy.Imagine I have a software for all the pharmacy. So basically they will just log on to one site. Let's say a URL link now of course they will have their own database. Here is where my problem comes in. Imagine I have two pharmacist who wanted my software. I don't know how will i create a blank table for them. Shall I create a blank mdf (sql database for each)?I was thinking for example Pharmacy1 will enter Medications and stuff so basically you will have a MedicationTable with ID, Meaning, Dosage, etc. and of course when Pharmacy2 joins my Pharmacyweb, when I link his PharmacyID with the Medication, Pharmacy2 will see the medicationTable because they are just sharing a table.Is there a way for Pharmacy2 not to see Pharmacy1's table? and for example Pharmacy3 wants to join, it will be a blank MedicationTable for Pharmacy3 to see but in reality it has some Medications in it already that only specific pharmacy can see.I need advise please. Shall I create mdf for each (that will be alot though) or how will I hide tables from each other.I was thinking... PharmacyID -> MedicationID so that when Pharmacy2 enters it will just see its own Medications. Is that right>? |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2009-11-23 : 21:39:21
|
| Please let me know which pharmacies. I want to be sure I don't allow my personal/medical information to be stored by, or put my family's well being in the hands of a pharmacy that isn't willing to hire a professional to manage their information. |
 |
|
|
|
|
|
I actually need an advice on what to do