-
doing a history
Hi
I have over 100 members in an e-commerce site,i want to do a history of each member:
-In which date he has registered to the site for the first time.
-When he stopped his account
-When he reopen his account...
-How many tutorials he has registered for during each period of his membership
For example if from "Date1" to "Date2",he had 1 registered tutorials
from "Date3" to "Date4",he had 4 registered tutorials
from "Date4" to "Date5",he had 2 registered tutorials
EveryTime the profile or the number of tutorials assigned to a specific member change(even though if he did a slight change),i want to be able to track it and saving it.
I have no clue about how to do this project.
Can anyone guide me?
thanks in advance
-
Re: doing a history
Well we have no clue as you have just given us an english description of what you want. What we now need is a technical description :), what lauguage is it written in, what format is the data, where is the data? SQL, access? How do you wish to view this, printed report, on screen, output to a file ?
-
Re: doing a history
since u donot know where to start from, maybe u should hire somebody to do a requirement analysis/system development. or if u want to do it yourself and need our help, you need to provide more technical details of what you want to be done. in short, the requierment analysis should be complete and should be in development phase so that we can help you on the portion you are stuck in.
-
Re: doing a history
Well I am using VB6 and i wish to store all the member's informations into an SQL server 2000 table.I want that when I click into a member's name in a VB6 form to view his history on screen and upon pressing on Print command, to have printed report.
-
Re: doing a history
in that case u need a couple of new tables
1. activity list : the list of activities available in your portal like opening account, closing account, uploading tutorial etc.
2. activity dates : the dates where the activities are stored. remember to use a key to define the member's account id
this way u can have all data stored in your db. the dates table should be updated every time any user conducts any activity. then u can use your vb frontend to load that info thru a sql query very easily.
since i dont know about your portal or your code or any other descriptions, i cannot comment on how you should approach further coding or development process.