Hi,

Thanks for your reply. But this will not work for us. Because we are having user table as well as the UserLogin Table which is going to maintain the login and logout information of the user. and from that UserLogin table we are having other tables which are dependent on them. If we go with the DNN login procedure then  we are having a lot many changes into our sytem, which is time effective. Can you please tell me how can we customise the login module according to our requirement?

Nipa

Hi,

Thanks for the reply.

This is really cool. But my requirement is quite extended. I am having the following three table.

1) UserMaster: Maintain the Users

Fields: UserName, Password, FirstName, LastName, .........

2) UserLoginTransaction: Maintain the UserLogin Records

Fields: TransactionNumber, UserName,LoginTimje,LogoutTime,..........

3) VoiceFileTable:Maintain the voice files uploaded by Users.

Fields: Transcriptionid, TransactionNumber(Ref. UserLoginTransaction), UserName(Ref. UserMaster), VocieFileName, voiceFilePath, ........

When user uploades the file then first they needs to login. Upon login unique transaction number will be generated and the login information will be entered to the UserLogInTransction Table. When user upload the files first the last transaction number will be taken from the UserLoginTransaction and then that is going to be added to the VoiceFileTable along with the username.

So my problem is that when we move all the users to the DNN user table, how can we enter the login details to the 'UserLoginTransaction' which we needs to enter into the voiceFileTable and rest of the tables are depends on that.