Jump to content

rudyten

New Members
  • Posts

    4
  • Joined

  • Last visited

    Never

Profile Information

  • Gender
    Not Telling
  • Location
    LA

rudyten's Achievements

Newbie

Newbie (1/5)

0

Reputation

  1. Am just wondering what the standards are or what people think. I tend to display a Success/fail message after every update to the database. My messages tend to be very detailed. instead of just "record failed". it will say "telephone added ok", "customer information updated". Maybe am going message happy, Same thing goes to confirmation messages, specially on deletes. my other issue is where to display the messages, I tend to push the page content down 2 lines to make room for the messages, Should I use a pop up instead? thanks:)
  2. need help. am learning php oop. Logic below breaks when processing second parent. $db was defined a second time? Suggestions? Do i need to define new database for child??? $db = new Database; $Query = ('Select parentId from PARENT'); $db->query($Query); while ($db->nextRecord()){ $PARENT_ID = $db->Record['PARENT_ID']; $PARENT_NAME = $db->Record['PARENT_NAME']; $Query = ('Select * from CHILD where CHILD_PARENT_ID = $PARENT_ID'); $db->query($Query); while ($db->nextRecord()){ print "child name: $db->Record['CHILD_NAME']; } }
  3. Tried that already. lol The problem is not the browser. If I get on Google Chrome and hit refresh on that page the same thing will happen
  4. I am working on my localhost(pc) at home after I refresh my page about 6-10 straight I get stuck on "Waiting on localhost...". It just hangs there. I do not think it is apache, because if I close the browser(firefox), and then reopen my page, I am once again good for 6-10 refreshes before it gets stuck again. How would I go about figuring out this problem? I see no clues in my logs. I am just not sure where too start looking. Some advice would be very appreciated
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.