userId to another DB from ASPNETDB...!

leeWozyWarren · December 6th, 2011, 12:54 PM

I have a set of tables that a doctor uses to keep patient records. For example: client details, therapy notes, etc etc... There are three doctors in the practice.

Here is my question:

I want my logged in users (the doctors) to only be able to access the rows of data that they have created and not rows of data associated with another user. I understand from Imar that

Quote:

Membership.GetUser().ProviderUserKey

could be the answer... How would I use this though?

I would assume that the rows of data that the user creates (INSERTS) would have inserted their user ID into a column like UserId, for example.

If so, is this safe enough that other users wont be able to access the wrong rows of data?

And also, how do I get the userId data from the ASPNETDB.mdf to my own database safely?

Regards

Lee

Imar · December 6th, 2011, 02:32 PM

To get some ideas on how to implement some of this, take a look at chapter 17, page 641 and further. It show show to keep track of the user name using EF.

I don't know if that helps you though, as I don't know your current data access technology (EF, SqlDataSource, direct SQL and so on).

Cheers,

Imar

leeWozyWarren · December 6th, 2011, 02:47 PM

Thanks Imar.

I am putting this to use in a new project to test before I start setting up the real project.

So I have a default page which simple says to log in. from the log in screen it directs you to a profile page where the user can see their log in details and make any amendments. From here they can also create a new client ie a patients Id, Name, Date of birth.... and then for the userID or userName to be filled with the current users Id or name...

I will be using EF I think.

Lee

Imar · December 6th, 2011, 02:56 PM

Again, it all depends on what you implement and how. Maybe the pages I referred to will help you out if you're using the Data Controls. Alternatively, if you're hand coding pages (as explained in the book as well), this will be a lot easier.

So, I would start by defining a data access strategy and then ask specific follow up questions here.

Cheers,

Imar

leeWozyWarren · December 6th, 2011, 02:59 PM

Well ideally I would want to use page coding so that I can use a custom layout that doesn't rely on a gridview or Detailsview...

Imar · December 6th, 2011, 03:16 PM

Then build a model in EF, and use the Hand Coding scenario from the book. Adding the user name there is then quite easy,

Cheers,

Imar