Thanks Susan!
I ended up doing something similar to get around my problem. I created a "printers.dat" table and a query. I execute a routine to update the printers.dat and inserted a query lookup for the Printers field on my form.
One thing I didn't understand in your example: In the place where I would put the delimited list of drop-down options, you just execute your little program the *memory* file. How does Webster+ know that the contents of the memory file are to be used for the options? Does it just know that any *memory* file contains the options or is there some other secret.
Thanks also, Mike!
The program isn't a report but a setup definition for an automatic printing routine which will run in background. Part of the set up is to define which label printer is to be used, so I need to present a list of the valid printers, which might well change from one day to the next. I do save the user's choice in the profile definition file, but when the user is creating the definition, she needs to see all the available printers. I thought I could just put the printer list in a variable built in an executed routine and pass that variable back to the Webster+ web page. That was not working. I'll take a look at the reports.html and *report files to see if I can see what I was doing wrong.
Thanks for the help, both of you!
Phil