Would someone be so kind as to lend a helping hand to explain just how to process what I am trying to preform at I need this finished asap and am at a loss. I need the item to the database connecting it to the customer to the database connecting it to the Purchase to the database and I can't fiqure it out. Call me programming defiant. Any solutions or help would greatly be appreciated.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Help to complete Process
- Thread starter Dostani
- Start date
- Thread starter
- #3
OK for starters Windows server, ASP, access DB and little time. Second if you want to look at the DB I can zip it and place it for download. Right now what I have achieved so far is the rough draft of the site. KISS is what has been requested. I have 2 forms colecting the data and the third posting the data as a simple preview. At that point I am missing the glue or rather the implementation to track the records properly so that after the order is placed I can pull a completed order down to process it.
Hope this helps.
Hope this helps.
- Thread starter
- #5
is the site and the forms are there in steps. thanks for the present and future help.
Dostani
Dostani
1. Register to use the Keychain maker.
-- form submits to "action" page. this page 1st check to see if the username exsits and IF it does NOT exist then INSERTS the inforamtion from forms into DB
2. Log in to our keychain maker.
-- much like the 1st step except you do not insert a record but you redirect users if their name is already in the DB...and you will redirecr them to the next step
3. Enter the text and upload a picture to the Keychain maker.
--again, another form that will record UserID through hidden filed(so we know whihc user uploaded it) and all the other info entered. "ASPUpload"
4. View your personalized custom Keychain.
-- find the record just created by searchinng for userID that we "hiddenly" (what a word) entered when the order was made & display the information
5. Purchase your custom Keychain!!
--- well here is tricky part...how do u want them to "purchase" it....by CreditCard , check, paypal????do u want a full "shopping cart"....
Anyhow, this is the theory behind it all!
How much of ASP knowledge u have?
All the best!
> need more info?
:: don't click HERE ::
-- form submits to "action" page. this page 1st check to see if the username exsits and IF it does NOT exist then INSERTS the inforamtion from forms into DB
2. Log in to our keychain maker.
-- much like the 1st step except you do not insert a record but you redirect users if their name is already in the DB...and you will redirecr them to the next step
3. Enter the text and upload a picture to the Keychain maker.
--again, another form that will record UserID through hidden filed(so we know whihc user uploaded it) and all the other info entered. "ASPUpload"
4. View your personalized custom Keychain.
-- find the record just created by searchinng for userID that we "hiddenly" (what a word) entered when the order was made & display the information
5. Purchase your custom Keychain!!
--- well here is tricky part...how do u want them to "purchase" it....by CreditCard , check, paypal????do u want a full "shopping cart"....
Anyhow, this is the theory behind it all!
How much of ASP knowledge u have?
All the best!
> need more info?
:: don't click HERE ::
- Thread starter
- #7
1. The first page actually is set up for the "new users" to register at which point at this moment tracks the users name. If it does not exist it goes into the database. The second repeat is a actual log-in procedure that makes the username state a session variable. My understanding is that if many hit the page at one time this is not ging to be practical as a "UserID" autonumbering field. But I have noticed that DW not to helpfull in creation of session variables.
Step 2-3 yes that is correct except I would like to trap instead of Username a autonumber ID as the session and lock the record on the user.
4. Here is the next issue, once the record is displayed I need to have the uploaded pic generated to the keychain as a preview and heres a twist in B/W without losing the actual pic format.
5. Final process goes to Verisign for CC only purchase. using they're system for the purchase which I understand I will use they're form and security.
As for ASP knowledge "Practicing Magician" Learn quickly by example and very self taught. Learned Pascal when I was 17. That about sums it up
Robert
Step 2-3 yes that is correct except I would like to trap instead of Username a autonumber ID as the session and lock the record on the user.
4. Here is the next issue, once the record is displayed I need to have the uploaded pic generated to the keychain as a preview and heres a twist in B/W without losing the actual pic format.
5. Final process goes to Verisign for CC only purchase. using they're system for the purchase which I understand I will use they're form and security.
As for ASP knowledge "Practicing Magician" Learn quickly by example and very self taught. Learned Pascal when I was 17. That about sums it up
Robert
- Status
Similar threads
