We have an old FoxPro 2.6 app which runs on Win 95/98/ME printing to a CITOH
5000 impact printer using a TTY driver. These machines are to be replaced
with WinXP which seems to have dropped support for TTY. When we use the
native Windows driver some rows are shifted to the right by a few
characters.

Is doing a migration to VFP 8 the best solution to this issue? I have
access to the source and my first attempt ended with an error:
Fatal Error in Converter:
Error: Alias name is already in use.
Error Number: 24
Method: openfile
Offending Code: USE ...
File being processed: basw110.scx

I'm quite familiar with other IDE's (VB, PowerBuilder, .NET) and databases
(SQL Server, Oracle, Access) but haven't used FoxPro before. Program
functionality hasn't changed in years so we're not looking to do any coding
changes.

--
Neil Negandhi
negandhi@vex.net

Re: Migrating from FoxPro 2.6 to FoxPro 8.0 by Development

Development
Mon Nov 24 15:19:19 CST 2003

It will be a big effort migrating your 2.6 app to a Obeject oriented
langauge like Visual Foxpro.
Remember Visual Foxpro is Object oriented and to migrate code from Foxpro
2.6 you must be ready to rewrite a big portion of your application.



"Neil Negandhi" <negandhi@vex.net> wrote in message
news:Ot6JR5ssDHA.2244@TK2MSFTNGP09.phx.gbl...
> We have an old FoxPro 2.6 app which runs on Win 95/98/ME printing to a
CITOH
> 5000 impact printer using a TTY driver. These machines are to be replaced
> with WinXP which seems to have dropped support for TTY. When we use the
> native Windows driver some rows are shifted to the right by a few
> characters.
>
> Is doing a migration to VFP 8 the best solution to this issue? I have
> access to the source and my first attempt ended with an error:
> Fatal Error in Converter:
> Error: Alias name is already in use.
> Error Number: 24
> Method: openfile
> Offending Code: USE ...
> File being processed: basw110.scx
>
> I'm quite familiar with other IDE's (VB, PowerBuilder, .NET) and databases
> (SQL Server, Oracle, Access) but haven't used FoxPro before. Program
> functionality hasn't changed in years so we're not looking to do any
coding
> changes.
>
> --
> Neil Negandhi
> negandhi@vex.net
>
>



Re: Migrating from FoxPro 2.6 to FoxPro 8.0 by swdev2

swdev2
Mon Nov 24 20:27:34 CST 2003

Neil -
naaaaaaaaaaa
updating it to VFP 8 ain't the only answer.

Drill around - find some compatible drivers with that C ITOH beastie ..

Have you replaced the printers to something else, as well ?
lemme know your thoughts.
mondo regards [Bill]
--
William Sanders / Electronic Filing Group Remove the DOT BOB to reply via
email.
FREE LONG DISTANCE -> mailto:excel-info@efgroup.net
Free Satellite Receivers and installation ->
http://www.vmcsatellite.com/?aid=58456
mySql / VFP / MS-SQL
"Neil Negandhi" <negandhi@vex.net> wrote in message
news:Ot6JR5ssDHA.2244@TK2MSFTNGP09.phx.gbl...
> We have an old FoxPro 2.6 app which runs on Win 95/98/ME printing to a
CITOH
> 5000 impact printer using a TTY driver. These machines are to be replaced
[snip]



Re: Migrating from FoxPro 2.6 to FoxPro 8.0 by Cindy

Cindy
Mon Nov 24 21:35:08 CST 2003

In news: Ot6JR5ssDHA.2244@TK2MSFTNGP09.phx.gbl,
Neil Negandhi <negandhi@vex.net> wrote:
> We have an old FoxPro 2.6 app .....
> Is doing a migration to VFP 8 the best solution to this issue?

Hi Neil,

The Fox team at Microsoft has made a lot of effort to maintain backward
compatibility in Visual FoxPro, and in some cases you can run Fox2x code in
VFP with few changes. Xbase procedural code is totally reusable. Running an
SPR in VFP makes an ugly interface and you're better off re-doing the
screens, for example.

I think most VFP developers would say that the Fox2x to VFP converter
doesn't do that great a job. MicroEndeavors had a migration kit that has
worked well for some people - see
http://www.microendeavors.com/courseware/default.asp (my internet is flaky
right now so I can't verify that this link is still good).

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




Re: Migrating from FoxPro 2.6 to FoxPro 8.0 by Neil

Neil
Tue Nov 25 08:50:13 CST 2003

Cindy, that link takes me to a shopping site. I went to
http://www.microendeavours.com yesterday and looked all over for the
migration kit mentioned in this newsgroup - no luck. Once your connection
comes up can you please verify the link? Thanks.

--
Neil Negandhi
negandhi@vex.net

"Cindy Winegarden" <cindy.winegarden@mvps.org> wrote in message
news:el1qUZwsDHA.2392@TK2MSFTNGP10.phx.gbl...
> In news: Ot6JR5ssDHA.2244@TK2MSFTNGP09.phx.gbl,
> Neil Negandhi <negandhi@vex.net> wrote:
> > We have an old FoxPro 2.6 app .....
> > Is doing a migration to VFP 8 the best solution to this issue?
>
> Hi Neil,
>
> The Fox team at Microsoft has made a lot of effort to maintain backward
> compatibility in Visual FoxPro, and in some cases you can run Fox2x code
in
> VFP with few changes. Xbase procedural code is totally reusable. Running
an
> SPR in VFP makes an ugly interface and you're better off re-doing the
> screens, for example.
>
> I think most VFP developers would say that the Fox2x to VFP converter
> doesn't do that great a job. MicroEndeavors had a migration kit that has
> worked well for some people - see
> http://www.microendeavors.com/courseware/default.asp (my internet is flaky
> right now so I can't verify that this link is still good).
>
> --
> Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
> cindy.winegarden@mvps.org www.cindywinegarden.com
>
>
>



Re: Migrating from FoxPro 2.6 to FoxPro 8.0 by Rick

Rick
Tue Nov 25 13:12:37 CST 2003

Neil, Cindy,
I just checked, and it looks like they've not only reworked the web =
site, but they don't appear to have any self-study courses listed. =
Perhaps if you called them they might still have a few copies laying =
around for a "discounted" price! In fact the only mention of FoxPro I =
could find is on their Home page! <s>

http://www.microendeavors.com/index.htm

Rick

"Neil Negandhi" <negandhi@vex.net> wrote in message =
news:uppx2N2sDHA.2508@TK2MSFTNGP12.phx.gbl...
> Cindy, that link takes me to a shopping site. I went to
> http://www.microendeavours.com yesterday and looked all over for the
> migration kit mentioned in this newsgroup - no luck. Once your =
connection
> comes up can you please verify the link? Thanks.
>=20
> --=20
> Neil Negandhi
> negandhi@vex.net
>=20
> "Cindy Winegarden" <cindy.winegarden@mvps.org> wrote in message
> news:el1qUZwsDHA.2392@TK2MSFTNGP10.phx.gbl...
> > In news: Ot6JR5ssDHA.2244@TK2MSFTNGP09.phx.gbl,
> > Neil Negandhi <negandhi@vex.net> wrote:
> > > We have an old FoxPro 2.6 app .....
> > > Is doing a migration to VFP 8 the best solution to this issue?
> >
> > Hi Neil,
> >
> > The Fox team at Microsoft has made a lot of effort to maintain =
backward
> > compatibility in Visual FoxPro, and in some cases you can run Fox2x =
code
> in
> > VFP with few changes. Xbase procedural code is totally reusable. =
Running
> an
> > SPR in VFP makes an ugly interface and you're better off re-doing =
the
> > screens, for example.
> >
> > I think most VFP developers would say that the Fox2x to VFP =
converter
> > doesn't do that great a job. MicroEndeavors had a migration kit that =
has
> > worked well for some people - see
> > http://www.microendeavors.com/courseware/default.asp (my internet is =
flaky
> > right now so I can't verify that this link is still good).
> >
> > --=20
> > Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
> > cindy.winegarden@mvps.org www.cindywinegarden.com
> >
> >
> >
>=20
>

Re: Migrating from FoxPro 2.6 to FoxPro 8.0 by Neil

Neil
Wed Nov 26 08:30:27 CST 2003

Thanks Rick. Sounds as if you've gone through this process before. Can you
give a (very) rough estimate on how long it would take to convert a 100
screen app? From what I can see, it's mostly reports and data entry screens
and not a lot of back end logic.

--
Neil Negandhi
negandhi@vex.net

"Rick Bean" <rgbean@unrealmelange-inc.com> wrote in message
news:OnLRYg4sDHA.3236@tk2msftngp13.phx.gbl...
Neil, Cindy,
I just checked, and it looks like they've not only reworked the web site,
but they don't appear to have any self-study courses listed. Perhaps if you
called them they might still have a few copies laying around for a
"discounted" price! In fact the only mention of FoxPro I could find is on
their Home page! <s>

http://www.microendeavors.com/index.htm

Rick

"Neil Negandhi" <negandhi@vex.net> wrote in message
news:uppx2N2sDHA.2508@TK2MSFTNGP12.phx.gbl...
> Cindy, that link takes me to a shopping site. I went to
> http://www.microendeavours.com yesterday and looked all over for the
> migration kit mentioned in this newsgroup - no luck. Once your connection
> comes up can you please verify the link? Thanks.
>
> --
> Neil Negandhi
> negandhi@vex.net
>
> "Cindy Winegarden" <cindy.winegarden@mvps.org> wrote in message
> news:el1qUZwsDHA.2392@TK2MSFTNGP10.phx.gbl...
> > In news: Ot6JR5ssDHA.2244@TK2MSFTNGP09.phx.gbl,
> > Neil Negandhi <negandhi@vex.net> wrote:
> > > We have an old FoxPro 2.6 app .....
> > > Is doing a migration to VFP 8 the best solution to this issue?
> >
> > Hi Neil,
> >
> > The Fox team at Microsoft has made a lot of effort to maintain backward
> > compatibility in Visual FoxPro, and in some cases you can run Fox2x code
> in
> > VFP with few changes. Xbase procedural code is totally reusable. Running
> an
> > SPR in VFP makes an ugly interface and you're better off re-doing the
> > screens, for example.
> >
> > I think most VFP developers would say that the Fox2x to VFP converter
> > doesn't do that great a job. MicroEndeavors had a migration kit that has
> > worked well for some people - see
> > http://www.microendeavors.com/courseware/default.asp (my internet is
flaky
> > right now so I can't verify that this link is still good).
> >
> > --
> > Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
> > cindy.winegarden@mvps.org www.cindywinegarden.com
> >
> >
> >
>
>



Re: Migrating from FoxPro 2.6 to FoxPro 8.0 by Rick

Rick
Wed Nov 26 09:48:53 CST 2003

Neil,
I've converted a number of projects from FPW 2.6a to VFP 6.0, and they =
ranged from "trivial" to most difficult. If you are going from FP DOS to =
VFP 8.0, you'll have an even more difficult time. A lot depends on the =
complexity of the forms and reports and whether you use any "kludges" =
and any non-FP code (e.g. PLB and BIN files). I've "converted" from DOS =
to FPW, and that was just very time consuming and tedious to deal with =
all the form and report changes due to the non-proportional differences =
for field sizes. (Windows users really expect that you don't used fixed =
width fonts much - if at all!)

The key, is to have a plan set up to do it, and not allowing the code to =
be changed while you are converting. Deciding on a "framework" of =
appropriate classes can also speed up the process. I'd really suggest =
you see if MEI still has that Self-Study course available - it made all =
the difference for our conversions. It includes a number "why's" and =
"how to's", as well as some useful utilities to assist in the process. =
One of their techniques allows a gradual transition using a mixed model, =
but there are some downsides as you might expect. Also, one utility can =
create forms from the running code - you don't even have to have =
"screens" (.SCX files) to convert them. For the price - $249 that last =
time I checked - you can't get better advice. (I have no connection with =
them, other than being a satisfied customer.)

Of course most people that have gone through this would suggest that the =
best idea is to forget converting, and just rewrite the application - in =
the long run it'll take less time AND you'll be happier with the end =
result.=20

You may also want to check out the new "Painless Legacy FoxPro =
Applications On Modern Networks (ebook only)" available at =
http://www.hentzenwerke.com/catalogpricelists/painlesse.htm.=20

Rick

"Neil Negandhi" <negandhi@vex.net> wrote in message =
news:OXo2XnCtDHA.2400@tk2msftngp13.phx.gbl...
> Thanks Rick. Sounds as if you've gone through this process before. =
Can you
> give a (very) rough estimate on how long it would take to convert a =
100
> screen app? From what I can see, it's mostly reports and data entry =
screens
> and not a lot of back end logic.
>=20
> --=20
> Neil Negandhi
> negandhi@vex.net
>=20
> "Rick Bean" <rgbean@unrealmelange-inc.com> wrote in message
> news:OnLRYg4sDHA.3236@tk2msftngp13.phx.gbl...
> Neil, Cindy,
> I just checked, and it looks like they've not only reworked the web =
site,
> but they don't appear to have any self-study courses listed. Perhaps =
if you
> called them they might still have a few copies laying around for a
> "discounted" price! In fact the only mention of FoxPro I could find is =
on
> their Home page! <s>
>=20
> http://www.microendeavors.com/index.htm
>=20
> Rick
>=20
> "Neil Negandhi" <negandhi@vex.net> wrote in message
> news:uppx2N2sDHA.2508@TK2MSFTNGP12.phx.gbl...
> > Cindy, that link takes me to a shopping site. I went to
> > http://www.microendeavours.com yesterday and looked all over for the
> > migration kit mentioned in this newsgroup - no luck. Once your =
connection
> > comes up can you please verify the link? Thanks.
> >
> > --=20
> > Neil Negandhi
> > negandhi@vex.net
> >
> > "Cindy Winegarden" <cindy.winegarden@mvps.org> wrote in message
> > news:el1qUZwsDHA.2392@TK2MSFTNGP10.phx.gbl...
> > > In news: Ot6JR5ssDHA.2244@TK2MSFTNGP09.phx.gbl,
> > > Neil Negandhi <negandhi@vex.net> wrote:
> > > > We have an old FoxPro 2.6 app .....
> > > > Is doing a migration to VFP 8 the best solution to this issue?
> > >
> > > Hi Neil,
> > >
> > > The Fox team at Microsoft has made a lot of effort to maintain =
backward
> > > compatibility in Visual FoxPro, and in some cases you can run =
Fox2x code
> > in
> > > VFP with few changes. Xbase procedural code is totally reusable. =
Running
> > an
> > > SPR in VFP makes an ugly interface and you're better off re-doing =
the
> > > screens, for example.
> > >
> > > I think most VFP developers would say that the Fox2x to VFP =
converter
> > > doesn't do that great a job. MicroEndeavors had a migration kit =
that has
> > > worked well for some people - see
> > > http://www.microendeavors.com/courseware/default.asp (my internet =
is
> flaky
> > > right now so I can't verify that this link is still good).
> > >
> > > --=20
> > > Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
> > > cindy.winegarden@mvps.org www.cindywinegarden.com
> > >
> > >
> > >
> >
> >
>=20
>

Migrating from FoxPro 2.6 to FoxPro 8.0 by Amer

Amer
Wed Nov 26 15:06:38 CST 2003

I highly recommend that you re-write your application to
migrate to VFP8.0, don't even waste your time.

Amer

>-----Original Message-----
>We have an old FoxPro 2.6 app which runs on Win 95/98/ME
printing to a CITOH
>5000 impact printer using a TTY driver. These machines
are to be replaced
>with WinXP which seems to have dropped support for TTY.
When we use the
>native Windows driver some rows are shifted to the right
by a few
>characters.
>
>Is doing a migration to VFP 8 the best solution to this
issue? I have
>access to the source and my first attempt ended with an
error:
>Fatal Error in Converter:
>Error: Alias name is already in use.
>Error Number: 24
>Method: openfile
>Offending Code: USE ...
>File being processed: basw110.scx
>
>I'm quite familiar with other IDE's (VB,
PowerBuilder, .NET) and databases
>(SQL Server, Oracle, Access) but haven't used FoxPro
before. Program
>functionality hasn't changed in years so we're not
looking to do any coding
>changes.
>
>--
>Neil Negandhi
>negandhi@vex.net
>
>
>.
>