OOOOOOOPS!
SORRY. Too many environments. (VFP, FPW) It's not a form, it's a report. I'm calling it a form because it looks like a form. It's a report.

Looks like the best answer I have is to put the data into a table and REPORT(!) it. That way I can rerun just the REPORT(!) with having to rerun the application. Sometimes I'm just too tricky for my own good.

Pete

ps George,
Great tip, thanks

>Preview ? As far as I remember there wasn't preview for forms. Is this a form or report ?
>Cetin
>
>>Cetin,
>>Thanks for the reply.
>>The only textboxes I have on the form are on the order of: a_filsize[6,2].
>>
>>If I just click on PREVIEW while I'm editing the form, the first thing that pops up is a dialog box asking for a table. That's the problem. Is there a way around this behavior?
>>Pete
>>
>>
>>>>Hi all,
>>>>It's me again with yet another oddball question for you FPW2.6 meisters.
>>>>
>>>>I'm calling a form at the end an app that I just want to plug data into from Memvars and arrays, not a table. When I run the app, the form wants a table. If I specify a table, the form repeats the data for however many records are in the table. Do I have to create a empty table to satisfy this or is there a little trick I can do? Since I have various fonts and indentations, no graphics (yet), I can't just dump the data to a text file and print it.
>>>>
>>>>Pete
>>>
>>>Pete,
>>>If you would just use memvars and arrays you don't need a table. Be sure your textboxes (as I remember they were textbox there too - get objects) doesn't refer to a table (m.name not employee.name) and also any startup code that tries to fill in memvars from a table (a wizard was doing it). You could possibly find it easily checking the .SPR generated. Check for something like :
>>>use
>>>scatter memvar
>>>Cetin