Skip to main content
January 10, 2008
Question

recordsets....

  • January 10, 2008
  • 14 replies
  • 2167 views
Hello. I know this may be simple to many but I am going to ask it anyways because I am stumped badly. Ok I need to be able to pull up info from a database with people and info from each county in each state, do I have to create a recordset for each county selected? Do you have to create one for each time you try to display the details page also? Is there another way to do this? Please help! Sorry if this seems stupid to some but I am trying here!

Thanks!!!!
This topic has been closed for replies.

14 replies

February 13, 2008
yeah after they pay, it goes to a page (still on securepay) that says it was approved, and below it has a link that takes them to the form... which all works fine, but if they were to pick up on the address up top, they can retype it in there next time and bypass the payment.

i can put in the page or url, that the go to after the payment, which is the form. its a written out code from secure pay with my id and etc. but do i need to write this in the url or the actual form page?
Inspiring
February 12, 2008
lilbodi wrote:
> i am following you but i dont know how to find out witht the secure pay. it
> just has a set up where after the payment, you set the page it goes to.

Don't you get any type of acknowledgement from the payment system that
payment has been authorized?

--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/
February 12, 2008
will do by telling people, i actually recommended it to a few people stuck on the same thing i was...

i am following you but i dont know how to find out witht the secure pay. it just has a set up where after the payment, you set the page it goes to. with what you wrote, is that to go on my page in dreamweaver or do i need to get that on the after payment page??
Inspiring
January 10, 2008
lilbodi wrote:
> Hello. I know this may be simple to many but I am going to ask it anyways
> because I am stumped badly. Ok I need to be able to pull up info from a
> database with people and info from each county in each state, do I have to
> create a recordset for each county selected?

One recordset will do. You order the results by state and county using
an ORDER BY clause in your SQL. A simple example:

SELECT id, name, county, state
FROM myTable
ORDER BY state, county, name

> Do you have to create one for
> each time you try to display the details page also?

The details page needs just one recordset that uses a URL parameter
(usually the record's primary key) as a filter.

--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/
Inspiring
January 10, 2008
lilbodi wrote:
> ah ok makes much more sense now. when they click a state, they are sent to
> that states page. from there they can select a county to pull up the
> information, what is the best way to present the counties? drop down/menu
> list? list them on the page?

Most states are likely to have a lot of counties, so a drop-down would
probably be more sensible.

--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/
Inspiring
January 12, 2008
lilbodi wrote:
> so when i make this recordset, i can use it for all counties by using the
> 'where' for each county that can be used as one recordset right?

Why don't you try it? Or are you completely new to working with recordsets?

> with the drop down list, you link that search page to the results page where
> the recordset it that displays the data on the results page. am i on the right
> track? you dont need a recordset on the search page from what i read, or is
> that wrong?

There are many different ways of doing things. It's very common for
search pages to use a self-processing form, so when you click the search
button, the same page reloads, and processes the code to create the
recordset and display the results. Alternatively, you can send the
search criteria from the form to a separate results page. If you do
that, the recordset is, of course, in the results page.

--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/

lilbodi wrote:
> yes i am fairly new but you gotta learn sometime and i am not afraid to admit
> it. the problem is i have no data in my database yet, there will be some as it
> starts, like a forum in a sort.... so i think that is where i am getting
> confused.

Everybody has to start somewhere. Even I was a beginner once! So I
understand the dilemma you're facing. The best approach is to take
things gently. Don't try to build the killer application right from the
start. Build a few small test pages, get to know how everything fits
together. Start by creating a few insert, update, and delete pages.
Don't worry about the contents of the database. You'll make mistakes as
you go along, so it's best to have a test database to play with while
you're learning.

The key to building search pages is learning the way you build SELECT
queries so that your recordset contains only those results that you
actually want.

--
David Powers, Adobe Community Expert
Author, "The Essential Guide to Dreamweaver CS3" (friends of ED)
Author, "PHP Solutions" (friends of ED)
http://foundationphp.com/