navigation
a webmaster learning community
     Home    Register     Search      Help      Login    
FrontPage Alternative
Sponsors

Shopping Cart Software
Ecommerce software integrated into Frontpage, Dreamweaver and Golive templates. No monthly fees and available in ASP and PHP versions.

Website Templates
We also have a wide selection of Dreamweaver, Expression Web and Frontpage templates as well as webmaster tools and CSS layouts.

Frontpage website templates
Creative Website Templates for FrontPage, Dreamweaver, Flash, SwishMax

Search Forums
 

Advanced search
Recent Posts

 Todays Posts
 Most Active posts
 Posts since last visit
 My Recent Posts
 Mark posts read

 

Limiting DRW records

 
View related threads: (in this forum | in all forums)

Logged in as: Guest
Users viewing this topic: none
Printable Version 

All Forums >> Web Development >> ASP and Database >> Limiting DRW records
Page: [1]
 
hme1

 

Posts: 4
From: Martinez, CA. USA
Status: offline

 
Limiting DRW records - 3/21/2001 20:50:00   
I have a DRW with a query of an account number. I have set the search to return 1 record. My problem is this: The DRW always shows the last person that created a profile. I am trying to create a DRW where it would be blank and the person would have to enter there account number to bring up their user information. Any thoughts on how to do this? Do I create a fictitious record that will always be in place as a default?
Mojo

 

Posts: 2441
From: Chicago
Status: offline

 
RE: Limiting DRW records - 3/21/2001 20:03:00   
If I understand your concerns correctly... here are a few things you can do.

You are correct about having a default record in place. Use something that will never come up like ux87tz45. The problem with this method is your DRW page will always show "Record not found" or whatever your default is when someone first goes there. You could make that blank, but then if a user enters their account number in wrong, the screen would just flash and there would be no message.

The better option may be to separate the input form from the DRW. You would have a page with the field where the user would enter their account number. When they pressed submit the information would be sent to your new DRW page and processed from their. There should be no noticeable difference in performance.

If you would like to go that route I (we) could walk you through it...

Joe


(in reply to hme1)
Page:   [1]

All Forums >> Web Development >> ASP and Database >> Limiting DRW records
Page: [1]
Jump to: 1





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts