ahhh, ok.
So the first page is the form with the drop-down box. The user selects a value and you POST to the second page.
The second page uses the POSTed variable to retrieve values from a db and display on the screen. It (the second page) also has a <b><META http-equiv="refresh" content="2; URL=http://www.mySite.com/page2.php"></b> in it to refresh the page and thereby updating the listed data with whatever has been recently added to the db.
ok.
First off, this is <i>not</i> a GLOBAL variable issue. <b>GLOBAL</b> scope refers to the context of the variable within a single script execution. When the second page refreshes, it is a new page execution and all variables from the previous execution (ie: the form POST) are gone.
What you want is actually <b>data persistence</b>. This means keeping data around from one script execution to the next. The standard way of doing this is to store the variable into a cookie or simply as as session variable the first time page2.php loads. Then on each refresh, read the value from the cookie or from the session variable.
In your case, you could achieve the same thing just by building the variable from the first POST right into the meta-refresh tag. If the variable from the drop down was <b>id</b>, then output the refresh tag like so:
<b>print "<META http-equiv=\"refresh\" content=\"10; URL=http://www.mySite.com/page2.php?id=$id\"></b>
This way, when the page refreshes, the variable will be there again. The only caviat is that if you have to reference the variable from HTTP_POST_VARS[] the first time and from HTTP_GET_VARS[] for the refreshed pages.
HTH
-- Rich