Re: Populate picklist from directory and return file name

In article <1126636683.912701.98450@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
"sunbum" <mbrashars@xxxxxxxxx> wrote:

> No, it worked great!
>
> I think our messages just crossed.
>
> It was the back slashes in my file path. Your code was perfect :)
>
> Do you have any pointers on this....
>
> > One last thing to bug you..... what holds the final selection of the
> > file? is it $file[select] ?
> > and what would signal that I am done selecting and want to do something
> > with the value?

You are outputting a form, that will look something like this:

<select name='file'>
<option value='bonjour.txt'>bonjour.txt</option>
<option value='hello.txt'>hello.txt</option>
</select>

When you submit that form, it will be put in $_GET["file"] on the receiving PHP
script.


--
Sandman[.net]
.

Relevant Pages

  • Re: Populate picklist from directory and return file name
    ... It was the back slashes in my file path. ... what holds the final selection of the ... Prev by Date: ...
    (comp.lang.php)
  • RE: input file
    ... I'm trying to use file path for my file that I want to read but I am ... You are getting confused with backward and forward slashes. ... the die string with a newline, as it prevents die from displaying the ... push @array, join "\t", @data; ...
    (perl.beginners)
  • Re: text selection
    ... selection within a text area. ... My users are in the habit of delineating ... options within anecdotal text using forward slashes, ...
    (comp.lang.javascript)
  • Determine Full Path of an Opened XL File
    ... While having a workbook XL file opened, is there a way/menu selection ... that will allow me to see the full file path (under Windows XPpro)? ...
    (microsoft.public.excel)
  • Re: Retrieving a File Path from the Registry in C#
    ... without ending up with a string which has all the slashes escaped which make ... I can see the file path in the registry using ... The debugger is showing the string with the slashes, ... the value to the console and you should see that it is in fact correct. ...
    (microsoft.public.dotnet.languages.csharp)