Anders
Tue Mar 29 04:33:54 CST 2005
That's the factory setup, yes. I figured he might have changed it.
-Anders
"Dan Freeman" <spam@microsoft.com> wrote in message
news:OdP4OK8MFHA.1268@TK2MSFTNGP14.phx.gbl...
> SET REPORTBEHAVIOR 80 is the default, isn't it?
>
> Dan
>
> Anders Altberg wrote:
> > Using VFP9, if you want your VFP8 reports to run like they used to
> > without conversion the best bet is to SET REPORTBEVHAVIOR 80 I
> > suppose. -Anders
> >
> > "Jake" <jStoddard@hotMailCCC.com> wrote in message
> > news:flkd415jd5mb0bqrghre7od7rb16p9qfaa@4ax.com...
> >> I did not. Is that a requirement? The reports all open correctly
> >> now, but I haven't actually tried to print anything yet.
> >>
> >> On Sun, 27 Mar 2005 00:26:11 +0100, "Anders Altberg"
> >> <x_pragma@telia.com> wrote:
> >>
> >>> Did you do a SET REPORTBEHAVIOR 80 to run the reports as in VFP8.
> >>> -Anders
> >>>
> >>> "Jake" <jStoddard@hotMailCCC.com> wrote in message
> >>> news:bjta41hr931la94b520v970cgregl9j7qn@4ax.com...
> >>>> That did not seem to fix the problem. I am not so sure that
> >>>> moving to VFP 9 is the right thing to do at this point. This app
> >>>> is comprised of approx 200 forms, 150 tables, 150 reports. When I
> >>>> first tried converting to 9, my entire project was destroyed when
> >>>> I tried to open some reports. I am not doing anything fancy here,
> >>>> base classes, but I keep having these unexplainable problems.
> >>>>
> >>>> Are there any dangers in compiling in 9 and then going back to 7??
> >>>>
> >>>> On Fri, 25 Mar 2005 22:31:21 GMT, Leemi@online.microsoft.com (Lee
> >>>> Mitchell) wrote:
> >>>>
> >>>>> Hi Jake:
> >>>>>
> >>>>> Did you try recompiling the from in VFP 9.0 (COMPILE FORM
> >>>>> form_name)?
> >>>>>
> >>>>> Is the option group from a class? If so, recompile the class
> >>>>> (COMPILE CLASS Class_name).
> >>>>>
> >>>>> I hope this helps.
> >>>>>
> >>>>> This posting is provided "AS IS" with no warranties, and confers
> >>>>> no rights.
> >>>>>
> >>>>> Sincerely,
> >>>>> Microsoft FoxPro Technical Support
> >>>>> Lee Mitchell
> >>>>>
> >>>>> *-- VFP9 HAS ARRIVED!! --*
> >>>>> Read about all the new features of VFP9 here:
> >>>>>
http://msdn.microsoft.com/vfoxpro/
> >>>>>
> >>>>> *--Purchase VFP 9.0 here:
> >>>>
> >>
> >>>
>
http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=54787e64-
> >>> 5 2
> >>>>> 69-4500-8bf2-3f06689f4ab3&type=ovr
> >>>>>
> >>>>> Keep an eye on the product lifecycle for Visual FoxPro here:
> >>>>>
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
> >>>>> - VFP5 Mainstream Support retired June 30th, 2003
> >>>>> - VFP6 Mainstream Support retired Sept. 30th, 2003
> >>>>>
> >>>>>
> >>>>>> Something fishy's going on. That's not normal.
> >>>>>
> >>>>>
> >>>>>> "Jake" <jStoddard@hotMailCCC.com> wrote in message
> >>>>>> news:qps641djodul0oqrdjlu942676gng0md88@4ax.com...
> >>>>>> Jeez, I am upgrading my VFP 7 application to VFP 9 and what the
> >>>>>> heck happened to the size of the radio buttons on the
> >>>>>> OptionGroup. I can hardly see them. I had to bump the font
> >>>>>> size to 11 before they were actually selectable.
>
>