I have an app that was written in 2.6 or 2.6a Foxpro.

I need to amend some report layouts.

They load up fine in VPRO 8 but get converted so that I can no longer use
them in my app.

Is there a solution to this problem?

I'd rather not install version 2.6 (even if I can still get hold of a copy!)

thanks,

jON

Re: Version 2.6 reports by Jeff

Jeff
Mon Sep 20 13:30:34 CDT 2004

I also maintain some 2.6 apps. As far as I know you must edit 2.6 reports in
2.6. The apps that I maintain are in 2.6 for DOS.

Copies of 2.6 are available. There is one source that sells all of the
outdated database packages. They also show up on ebay from time to time.

Regards,
Jeff

"Jon Rowlan" <jon.rowlan@sads.com> wrote in message
news:eoHRUtznEHA.3756@TK2MSFTNGP11.phx.gbl...
> I have an app that was written in 2.6 or 2.6a Foxpro.
>
> I need to amend some report layouts.
>
> They load up fine in VPRO 8 but get converted so that I can no longer use
> them in my app.
>
> Is there a solution to this problem?
>
> I'd rather not install version 2.6 (even if I can still get hold of a
copy!)
>
> thanks,
>
> jON
>
>



Re: Version 2.6 reports by Cindy

Cindy
Mon Sep 20 14:07:00 CDT 2004

Hi Jon,

In addition to Jeff's suggestions you might be able to pay someone to do the
work for you. It may be cheaper than buying a Fox2.6 license.

--
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy.winegarden@mvps.org www.cindywinegarden.com


"Jon Rowlan" <jon.rowlan@sads.com> wrote in message
news:eoHRUtznEHA.3756@TK2MSFTNGP11.phx.gbl...
>I have an app that was written in 2.6 or 2.6a Foxpro.
>
> I need to amend some report layouts.



Re: Version 2.6 reports by Andrew

Andrew
Tue Sep 21 02:52:38 CDT 2004

Jon Rowlan wrote:
> I have an app that was written in 2.6 or 2.6a Foxpro.
>
> I need to amend some report layouts.
>
> They load up fine in VPRO 8 but get converted so that I can no longer
> use them in my app.
>
> Is there a solution to this problem?
>
> I'd rather not install version 2.6 (even if I can still get hold of a
> copy!)


If it's fairly straightforward, or you can tell me what to do and there
isn't too much, I'll change them for you (I have FPW2.6a) - email if
interested to "andrew dot howell at gmail d0t com" - if it's going to be an
ongoing thing this is maybe not a great solution but I can certainly handle
a one off.

--
Regards
Andrew Howell



Re: Version 2.6 reports by Jon

Jon
Wed Sep 22 02:21:25 CDT 2004

Thanks for the suggestion guys, unfortunately for me, this is an ongoing
thing and I have a fair amount of work to do.

The customer will not bear the cost.

Unless I can find a way its a no go.

I have dug out my 2.5 diskettes ... does anyone know if the report format
changed from 2.5 to 2.6?

Why is 2.6 so hard to get hold of??

jON


"Andrew Howell" <ajh@work> wrote in message
news:eTgpAA7nEHA.556@tk2msftngp13.phx.gbl...
> Jon Rowlan wrote:
> > I have an app that was written in 2.6 or 2.6a Foxpro.
> >
> > I need to amend some report layouts.
> >
> > They load up fine in VPRO 8 but get converted so that I can no longer
> > use them in my app.
> >
> > Is there a solution to this problem?
> >
> > I'd rather not install version 2.6 (even if I can still get hold of a
> > copy!)
>
>
> If it's fairly straightforward, or you can tell me what to do and there
> isn't too much, I'll change them for you (I have FPW2.6a) - email if
> interested to "andrew dot howell at gmail d0t com" - if it's going to be
an
> ongoing thing this is maybe not a great solution but I can certainly
handle
> a one off.
>
> --
> Regards
> Andrew Howell
>
>



Re: Version 2.6 reports by Andrew

Andrew
Wed Sep 22 03:07:43 CDT 2004

Jon Rowlan wrote:
> Thanks for the suggestion guys, unfortunately for me, this is an
> ongoing thing and I have a fair amount of work to do.
>
> The customer will not bear the cost.

I was offering to do it for nothing although you just pointed out it's an
ongoing thing which I can't spare the time to do..

>
> Unless I can find a way its a no go.
>
> I have dug out my 2.5 diskettes ... does anyone know if the report
> format changed from 2.5 to 2.6?

In the back of my 2.6 manual it describes the report file structure as
"Foxpro 2.0 Report File Structure" - this would suggest that nothing much
changed but before all the file structures it does say "The structures of
these data files are subject to change."

Then I had a better idea. I looked through the code for the transporter
program [automatically invoked to update reports/screens/labels opened in
the development environment to 2.6 format.]

From what I can gather, 2.5 and 2.6 are handled the same for reports, so
based on that I would say they are the same. The "version identifier" in the
actual .FRX file is the same for 2.5 and 2.6 also (top record of .FRX,
objtype=1 for report, objcode=53 for v2.5)

>
> Why is 2.6 so hard to get hold of??

I thought it was the most readily available of the 2.x series, it is over a
decade old after all.
http://www.emsps.com/oldtools/msfox.htm#foxprowin26

But anyway, it sounds as if your 2.5 should be good for modifyiung reports.
Fingers crossed they still work.

Regards
Andrew Howell



Re: Version 2.6 reports by Jon

Jon
Wed Sep 22 09:57:57 CDT 2004

Thanks Andrew, I really do appreciate the offer but the work escalated today
to half a dozen reports and some update programs !

I have however dug out some old 2.6a diskettes ... but these seem to be for
a DOS version ... is 2.6a for DOS the same thing as 2.6a for Windows ... I
don't remember ... or is 2.6a a DOS development desktop with a Windows
"emulator" for runtime?

jON





"Andrew Howell" <ajh@work> wrote in message
news:upNRJtHoEHA.648@tk2msftngp13.phx.gbl...
> Jon Rowlan wrote:
> > Thanks for the suggestion guys, unfortunately for me, this is an
> > ongoing thing and I have a fair amount of work to do.
> >
> > The customer will not bear the cost.
>
> I was offering to do it for nothing although you just pointed out it's an
> ongoing thing which I can't spare the time to do..
>
> >
> > Unless I can find a way its a no go.
> >
> > I have dug out my 2.5 diskettes ... does anyone know if the report
> > format changed from 2.5 to 2.6?
>
> In the back of my 2.6 manual it describes the report file structure as
> "Foxpro 2.0 Report File Structure" - this would suggest that nothing much
> changed but before all the file structures it does say "The structures of
> these data files are subject to change."
>
> Then I had a better idea. I looked through the code for the transporter
> program [automatically invoked to update reports/screens/labels opened in
> the development environment to 2.6 format.]
>
> From what I can gather, 2.5 and 2.6 are handled the same for reports, so
> based on that I would say they are the same. The "version identifier" in
the
> actual .FRX file is the same for 2.5 and 2.6 also (top record of .FRX,
> objtype=1 for report, objcode=53 for v2.5)
>
> >
> > Why is 2.6 so hard to get hold of??
>
> I thought it was the most readily available of the 2.x series, it is over
a
> decade old after all.
> http://www.emsps.com/oldtools/msfox.htm#foxprowin26
>
> But anyway, it sounds as if your 2.5 should be good for modifyiung
reports.
> Fingers crossed they still work.
>
> Regards
> Andrew Howell
>
>



Re: Version 2.6 reports by Rick

Rick
Wed Sep 22 13:38:40 CDT 2004

Jon,
Nope, FPD(OS) and FPW(indows) are two separate products, and while you =
can run the DOS reports under FPW, they won't support any of the =
"normal" Windows features - like fonts and fine adjustments.

Note: If you do find the FPW disks, you won't be able to install it on a =
newer computer (one that runs faster than ~250mHz), because the =
installer has the same "fast" CPU problem that FPW has. While you can =
fix FPW once it's installed, I've never seem a patch for the install. (I =
usually just copy the FPW files from an earlier install - I can do this =
because I was "granfathered" in the old Fox Software unlimited licence =
that MS respects.)

Rick

"Jon Rowlan" <jon.rowlan@sads.com> wrote in message =
news:u$LVQSLoEHA.556@tk2msftngp13.phx.gbl...
> Thanks Andrew, I really do appreciate the offer but the work escalated =
today
> to half a dozen reports and some update programs !
>=20
> I have however dug out some old 2.6a diskettes ... but these seem to =
be for
> a DOS version ... is 2.6a for DOS the same thing as 2.6a for Windows =
... I
> don't remember ... or is 2.6a a DOS development desktop with a Windows
> "emulator" for runtime?
>=20
> jON
>=20
>=20
>=20
>=20
>=20
> "Andrew Howell" <ajh@work> wrote in message
> news:upNRJtHoEHA.648@tk2msftngp13.phx.gbl...
>> Jon Rowlan wrote:
>> > Thanks for the suggestion guys, unfortunately for me, this is an
>> > ongoing thing and I have a fair amount of work to do.
>> >
>> > The customer will not bear the cost.
>>
>> I was offering to do it for nothing although you just pointed out =
it's an
>> ongoing thing which I can't spare the time to do..
>>
>> >
>> > Unless I can find a way its a no go.
>> >
>> > I have dug out my 2.5 diskettes ... does anyone know if the report
>> > format changed from 2.5 to 2.6?
>>
>> In the back of my 2.6 manual it describes the report file structure =
as
>> "Foxpro 2.0 Report File Structure" - this would suggest that nothing =
much
>> changed but before all the file structures it does say "The =
structures of
>> these data files are subject to change."
>>
>> Then I had a better idea. I looked through the code for the =
transporter
>> program [automatically invoked to update reports/screens/labels =
opened in
>> the development environment to 2.6 format.]
>>
>> From what I can gather, 2.5 and 2.6 are handled the same for reports, =
so
>> based on that I would say they are the same. The "version identifier" =
in
> the
>> actual .FRX file is the same for 2.5 and 2.6 also (top record of =
.FRX,
>> objtype=3D1 for report, objcode=3D53 for v2.5)
>>
>> >
>> > Why is 2.6 so hard to get hold of??
>>
>> I thought it was the most readily available of the 2.x series, it is =
over
> a
>> decade old after all.
>> http://www.emsps.com/oldtools/msfox.htm#foxprowin26
>>
>> But anyway, it sounds as if your 2.5 should be good for modifyiung
> reports.
>> Fingers crossed they still work.
>>
>> Regards
>> Andrew Howell
>>
>>
>=20
>