Fred,

You would think that since both the .lbx and .frx tables use identical structures that it would be easy to just pop that in. I'm constantly amazed, though, at what Microsoft chooses not to fix or change. My current pet peeve is that, if a user has an Excel worksheet with the zipcode column formatted in Excel's "zipcode" format, then those zipcodes will be converted to numbers when they export to a dbf table. 07543-1114 becomes 75431114. All the zeros are dropped from upper New England zipcodes. The Excel KB article on this says that this is "Excel's behavior" (not a bug) and gives a work around. You would think that, since this is a ZIPCODE format, Excel should be smart enough to know not to drop any zeros and not to convert it to numbers.

I'm sorry, you got me started. I'll quit now.

Thanks again for the REPORT FORM work around.

Ed

>Ed,
>
>Glad that helped. I wonder why the LABEL command doesn't support RANGE?
>
>
>>
>>>
>>>Have you tried using the REPORT FORM xxx.lbx RANGE x,y command? Reports and labels are nearly the same thing. I tried this and it does work, but does this do what you want it to?