Upgrade from FPW/DOS 2.6 to VFP6.0

I'm preparing to upgrade an application package that uses Foxpro 2.6 for
Windows/DOS, to a newer package that uses Visual Foxpro Version 6.

I have an opportunity to buy a used Upgrade version of VFP 6. Would
that version consider the old Version 2.6 a qualifying version for
upgrade purposes?

Thanks for your help.

Lakeside

Paul
Sat Feb 04 11:20:21 CST 2006

If you're going to all the trouble of upgrading a 2.6 app, why not go
straight to VFP9? Unless you have a good reason for sticking with 6, and I
can't think of any at the moment, the new features (including stability) of
9 are well worth the difference in price.

As far as answering your question, I don't know. Upgrade qualifications
might be written on the box. You might be able to find it on MS's site too,
but maybe not - that's ancient stuff. Even VFP7 is no longer officially
supported.


<me@privacy.net> wrote in message news:44itaeF2e0vaU2@individual.net...
> I'm preparing to upgrade an application package that uses Foxpro 2.6 for
> Windows/DOS, to a newer package that uses Visual Foxpro Version 6.
>
> I have an opportunity to buy a used Upgrade version of VFP 6. Would that
> version consider the old Version 2.6 a qualifying version for upgrade
> purposes?
>
> Thanks for your help.
>
> Lakeside

Cindy
Sat Feb 04 11:16:40 CST 2006

Please see my answer in the Chatter newsgroup. Please don't post the same
question multiple times to different newsgroups. Most of us here read all
the groups so we'll find your questions wherever they are.

--
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@msn.com www.cindywinegarden.com


<me@privacy.net> wrote in message news:44itaeF2e0vaU2@individual.net...
> I'm preparing to upgrade an application package that uses Foxpro 2.6 for
> Windows/DOS, to a newer package that uses Visual Foxpro Version 6.
>
> I have an opportunity to buy a used Upgrade version of VFP 6. Would that
> version consider the old Version 2.6 a qualifying version for upgrade
> purposes?
>
> Thanks for your help.
>
> Lakeside

me
Sun Feb 05 00:14:13 CST 2006

Paul Pedersen wrote:
> If you're going to all the trouble of upgrading a 2.6 app, why not go
> straight to VFP9? Unless you have a good reason for sticking with 6, and I
> can't think of any at the moment, the new features (including stability) of
> 9 are well worth the difference in price.

Unfortunately, the app specifies VFP6, primarily for compiling the
programs. I don't know enough about it yet to know if version 9 will be
overkill. Thanks for the answer, and the suggestions.

>
> As far as answering your question, I don't know. Upgrade qualifications
> might be written on the box. You might be able to find it on MS's site too,
> but maybe not - that's ancient stuff. Even VFP7 is no longer officially
> supported.
>
>
> <me@privacy.net> wrote in message news:44itaeF2e0vaU2@individual.net...
>
>>I'm preparing to upgrade an application package that uses Foxpro 2.6 for
>>Windows/DOS, to a newer package that uses Visual Foxpro Version 6.
>>
>>I have an opportunity to buy a used Upgrade version of VFP 6. Would that
>>version consider the old Version 2.6 a qualifying version for upgrade
>>purposes?
>>
>>Thanks for your help.
>>
>>Lakeside
>
>
>

me
Sun Feb 05 00:17:03 CST 2006

Cindy Winegarden wrote:

> Please see my answer in the Chatter newsgroup. Please don't post the same
> question multiple times to different newsgroups. Most of us here read all
> the groups so we'll find your questions wherever they are.
>

Sorry, didn't know this group was moderated.

Also, since this is my first visit to these groups, I really don't
recognize any of the names from group to group.

I find that frequently Usenet readers will post to multiple groups with
similar focus, just to catch those who DON'T read all the groups. Just
trying to cover all the bases I can.

me
Sun Feb 05 00:28:11 CST 2006

Cindy Winegarden wrote:

> Please see my answer in the Chatter newsgroup. Please don't post the same
> question multiple times to different newsgroups. Most of us here read all
> the groups so we'll find your questions wherever they are.
>

Cindy,

One other point re: posting to both of these groups. My news
server--news.individual.de--does not retain messages for much beyond 30
days. I note that it lists only some 54 messages in the .chatter group,
while it lists 6,727 messages in this group. As mentioned before, I'm
just trying for the best coverage I can get.

LS

Tim
Sun Feb 05 11:23:07 CST 2006

I currently run applications on both Foxprow 2.6 and on VFP6, which I
purchased when that was the latest version - I did not try to buy it as
an upgrade. I have found that I have to rewrite my old Foxprow
applications from scratch for VFP.

In article <44itaeF2e0vaU2@individual.net>, me@privacy.net writes
>I'm preparing to upgrade an application package that uses Foxpro 2.6
>for Windows/DOS, to a newer package that uses Visual Foxpro Version 6.
>
>I have an opportunity to buy a used Upgrade version of VFP 6. Would
>that version consider the old Version 2.6 a qualifying version for
>upgrade purposes?
>
>Thanks for your help.
>
>Lakeside

--
Tim Hobson

Paul
Sun Feb 05 11:40:03 CST 2006


<me@privacy.net> wrote in message news:44ljccF2oel9U1@individual.net...
> Unfortunately, the app specifies VFP6, primarily for compiling the
> programs.

I do not understand that statement.

With minor exceptions, anything that can be compiled in VFP6 will run just
fine in VFP9.


> I don't know enough about it yet to know if version 9 will be overkill.

I don't see how it would be "overkill". It's only a question of whether
VFP9's improved features (including still being supported by Microsoft) are
worth the extra expense to you. Include in your consideration the fact that
you'll be able to use VFP9 for your other projects as well.

Regarding your license question, I found a VFP6 upgrade edition for sale on
EBay. The ad said this:
You may upgrade from these following:
Microsoft FoxPro version 2.5 or later
Microsoft Visual Foxpro 3.0 or later
Visual FoxPro 3.0 for the power Macintosh

Of course, I can't guarantee the accuracy of what the EBay seller posted,
but it sounds reasonable.

I still recommend going straight to 9 though.

Paul
Sun Feb 05 12:01:00 CST 2006

I concur. Although it's "possible" to compile Fox 2.6 apps in VFP, the
results are ugly. And for all but the simplest applications, a rewrite is
strongly recommended, and might be necessary.


"Tim Hobson" <Tim@tjhobson.demon.co.uk> wrote in message
news:f1UirxB7Rj5DFwuC@tjhobson.demon.co.uk...
>I currently run applications on both Foxprow 2.6 and on VFP6, which I
>purchased when that was the latest version - I did not try to buy it as an
>upgrade. I have found that I have to rewrite my old Foxprow applications
>from scratch for VFP.
>
> In article <44itaeF2e0vaU2@individual.net>, me@privacy.net writes
>>I'm preparing to upgrade an application package that uses Foxpro 2.6 for
>>Windows/DOS, to a newer package that uses Visual Foxpro Version 6.
>>
>>I have an opportunity to buy a used Upgrade version of VFP 6. Would that
>>version consider the old Version 2.6 a qualifying version for upgrade
>>purposes?
>>
>>Thanks for your help.
>>
>>Lakeside
>
> --
> Tim Hobson

Cindy
Sun Feb 05 12:10:54 CST 2006

<me@privacy.net> wrote in message news:44ljhmF2oel9U2@individual.net...

> Sorry, didn't know this group was moderated.

I'ts not.

> I find that frequently Usenet readers will post to multiple groups with
> similar focus, just to catch those who DON'T read all the groups. Just
> trying to cover all the bases I can.

I don't know how your newsreader (Mozilla?) works but the best way of
posting to multiple groups is to make one post with several group names on
the Newsgroups line, not individual posts to more than one group. The
default reply behavior to this method is like Reply All in an email client.
The answers post to all of the groups listed, keeping all the discussions
together. Also, in Outlook Express at least when you've read the post in one
of the listed newsgroups it's marked read in all the groups. Again, I don't
know how your newsreader works.

--
Cindy Winegarden MCSD, Microsoft Visual FoxPro MVP
cindy_winegarden@msn.com www.cindywinegarden.com

me
Sun Feb 05 14:16:57 CST 2006

While I appreciate everyone's concern that I am seeking what is an
obviously out-of-date version of Visual FoxPro--and, while I stand
admonished for poor posting procedure and etiquette--I feel compelled to
point out that only one poster--Paul Pederson--addressed my original
question.

At the risk of wasting what is obviously precious bandwidth in this news
group, I also feel compelled to explain my reasons for such irrational
behavior.

I am going to be modifying--not developing--an application package
called SBT/Vision Point, Version 10. This package is considered a
"legacy" system by its distributor (formerly ACCPAC, now Sage), meaning
that it is OLD. (Truly, the source programs were written in 2001.)
But, the package fits the needs of my customer; and, he has been running
quite well on this system with modifications I put in place first more
than 10 years ago, and another set of changes in 1999 to prepare them
for the year 2000 situation. I will have to change only a small
percentage of the programs (perhaps 10%), but my modifications will have
to work with the remaining programs in this package. The documentation
supplied by the distributor plainly states that if one is going to be
modifying the source programs, Visual FoxPro Version 6.0 must be used to
compile the modified programs. The FoxPro runtime routines supplied are
from Version 6.0. Thus, my search for VFP6.0.

Paul, I did see that item on Ebay, and asked the seller to specifically
check the documentation for the eligibility of upgrade from FPW2.6.
Thank you very much for your search and input.

Perhaps my original request was poorly worded. It certainly appears
that my intelligence, and knowledge of Usenet, does not measure up to
that of the august posters/readers of this news group.

swdev2
Sun Feb 05 16:50:57 CST 2006

Heya Lakeside -

The Empower ISV Program includes a 5 license set of MSDN Universal
Subscription, which contains everything MS puts out, including Visual Studio
6.0 set, which includes VFP 6.0 .
There are some qualifications to get listed as an ISV, but its quite easy.
The price is right too - it's 375 for your year.
Check it out? www.empowerisv.com


I know you're on a quest - I read your trail about SBT. Good Luck with it -
hopefully you'll take the plunge and become an ISV as well.

Mondo Regards [Bill]
--
===================
William Sanders / EFG VFP / mySql / MS-SQL
www.efgroup.net/vfpwebhosting
www.terrafox.net www.viasqlserver.net

<me@privacy.net> wrote in message news:44itaeF2e0vaU2@individual.net...
> I'm preparing to upgrade an application package that uses Foxpro 2.6 for
> Windows/DOS, to a newer package that uses Visual Foxpro Version 6.
>
> I have an opportunity to buy a used Upgrade version of VFP 6. Would
> that version consider the old Version 2.6 a qualifying version for
> upgrade purposes?
>
> Thanks for your help.
>
> Lakeside

Imaginecorp
Sun Feb 05 21:53:56 CST 2006

<<<does not measure up to that of the august posters/readers of this news
group.>>

LOL
Boy people are pretty sensitive here aren't they? But I love your style of
writing...

VFP 6 if I remember right came bundled with Visual studio, I think we have
it some where at the office, I will check and if you need it, you can have
it for free, In return, if you are a SBT Accounting software expert, I may
call upon you for some programming help (if needed)

Let me know..

Mohammed
www.imaginecorp.com\whatwedo.htm

<me@privacy.net> wrote in message news:44n4q1F2vubgU1@individual.net...
> While I appreciate everyone's concern that I am seeking what is an
> obviously out-of-date version of Visual FoxPro--and, while I stand
> admonished for poor posting procedure and etiquette--I feel compelled to
> point out that only one poster--Paul Pederson--addressed my original
> question.
>
> At the risk of wasting what is obviously precious bandwidth in this news
> group, I also feel compelled to explain my reasons for such irrational
> behavior.
>
> I am going to be modifying--not developing--an application package called
> SBT/Vision Point, Version 10. This package is considered a "legacy"
> system by its distributor (formerly ACCPAC, now Sage), meaning that it is
> OLD. (Truly, the source programs were written in 2001.) But, the package
> fits the needs of my customer; and, he has been running quite well on this
> system with modifications I put in place first more than 10 years ago, and
> another set of changes in 1999 to prepare them for the year 2000
> situation. I will have to change only a small percentage of the programs
> (perhaps 10%), but my modifications will have to work with the remaining
> programs in this package. The documentation supplied by the distributor
> plainly states that if one is going to be modifying the source programs,
> Visual FoxPro Version 6.0 must be used to compile the modified programs.
> The FoxPro runtime routines supplied are from Version 6.0. Thus, my
> search for VFP6.0.
>
> Paul, I did see that item on Ebay, and asked the seller to specifically
> check the documentation for the eligibility of upgrade from FPW2.6. Thank
> you very much for your search and input.
>
> Perhaps my original request was poorly worded. It certainly appears that
> my intelligence, and knowledge of Usenet, does not measure up to that of
> the august posters/readers of this news group.
>
>

me
Sun Feb 05 22:34:33 CST 2006

MANY, MANY thanks, Bill!

I checked out the requirements and I probably can't qualify for a couple
of reasons. Firstly, I will not be developing anything; rather, I will
only be modifying an existing package. Secondly, neither my customer
nor myself have a web page.

I doubt that I would ever develop a package anyway. You see, I'm not a
PC man. I've spent most of my business life working on mainframe
systems, first as a programmer, then systems analyst, and lastly as an
instructor of operating system problem analysis, and assembly language
programming. I undertook this task as a favor to an old friend. He
couldn't seem to find anyone that could understand his business needs
and translate them to a programmed solution. He figured with my fairly
extensive background that I could do it. And, I figured: "Heck, if I
can program the equivalent of a small Cray, I can program anything!"
And, it has worked pretty darn well so far. But, I don't really enjoy
working in FoxPro. I keep this up because my "customer" is my oldest
and dearest friend. Of course, he pays me for my work; but, I don't
charge him nearly as much as anyone else would.

The Empower ISV program would certainly be the way to go--if I planned
to make this a continuing thing. But, I'm not trying to make a career
of this!

Again, many thanks, and my very best regards to you.

Jim Lamb
lakesidejim@cvalley.net

swdev2 wrote:

> Heya Lakeside -
>
> The Empower ISV Program includes a 5 license set of MSDN Universal
> Subscription, which contains everything MS puts out, including Visual Studio
> 6.0 set, which includes VFP 6.0 .
> There are some qualifications to get listed as an ISV, but its quite easy.
> The price is right too - it's 375 for your year.
> Check it out? www.empowerisv.com
>
>
> I know you're on a quest - I read your trail about SBT. Good Luck with it -
> hopefully you'll take the plunge and become an ISV as well.
>
> Mondo Regards [Bill]
> --
> ===================
> William Sanders / EFG VFP / mySql / MS-SQL
> www.efgroup.net/vfpwebhosting
> www.terrafox.net www.viasqlserver.net
>
> <me@privacy.net> wrote in message news:44itaeF2e0vaU2@individual.net...
>
>>I'm preparing to upgrade an application package that uses Foxpro 2.6 for
>>Windows/DOS, to a newer package that uses Visual Foxpro Version 6.
>>
>>I have an opportunity to buy a used Upgrade version of VFP 6. Would
>>that version consider the old Version 2.6 a qualifying version for
>>upgrade purposes?
>>
>>Thanks for your help.
>>
>>Lakeside
>
>
>

me
Sun Feb 05 22:42:43 CST 2006

Imaginecorp wrote:

> <<<does not measure up to that of the august posters/readers of this news
> group.>>
>
> LOL
> Boy people are pretty sensitive here aren't they? But I love your style of
> writing...

Thanks, Mohammed.

I only barked back because I got barked at!

I really don't consider myself an "SBT expert" (see my response to
"swdev2"). I've only worked with 5 modules in SBT, staring with Version
6, then 7, and now facing Version 10. So, I'm really not soliciting
work in this area--I have all I want keeping my customer/friend running.

I had seen the Upgrade version on Ebay that Paul mentioned and, since my
customer already has FPW2.6, I was curious to know if that would qualify
as an upgradeable version.

We're not free-loaders: I have no problem paying for the software--well,
having my "customer" pay for it (after all, it IS for him!). So, you
might want to consider setting a fair price for your Visual
Studio/VFP6.0; and, drop me a line at my E-mail address below.

Many thanks for your response, and your kind offer.

Best regards,

Jim Lamb
lakesidejim@cvalley.net

>
> VFP 6 if I remember right came bundled with Visual studio, I think we have
> it some where at the office, I will check and if you need it, you can have
> it for free, In return, if you are a SBT Accounting software expert, I may
> call upon you for some programming help (if needed)
>
> Let me know..
>
> Mohammed
> www.imaginecorp.com\whatwedo.htm
>

Paul
Mon Feb 06 00:07:51 CST 2006

Hmmm, I remember SBT. I did some work with that several years ago, back in
its 2.6 days.

I didn't know it was a maintenance job; I thought it was conversion. To
convert a large package like that when only a small change is needed does
indeed sound like a lot of work for not much benefit.

But if you have to convert the whole thing from 2.6 to VFP, 9 still might be
the way to go. Unless Sage is still supporting that old version and they
still insist on VFP6, I wouldn't be overly concerned about that requirement.

But if a small change is all that's needed, you might even be better off
staying with 2.6.

Don't be overly sensitive. We're all in the same boat here.



<me@privacy.net> wrote in message news:44n4q1F2vubgU1@individual.net...
> While I appreciate everyone's concern that I am seeking what is an
> obviously out-of-date version of Visual FoxPro--and, while I stand
> admonished for poor posting procedure and etiquette--I feel compelled to
> point out that only one poster--Paul Pederson--addressed my original
> question.
>
> At the risk of wasting what is obviously precious bandwidth in this news
> group, I also feel compelled to explain my reasons for such irrational
> behavior.
>
> I am going to be modifying--not developing--an application package called
> SBT/Vision Point, Version 10. This package is considered a "legacy"
> system by its distributor (formerly ACCPAC, now Sage), meaning that it is
> OLD. (Truly, the source programs were written in 2001.) But, the package
> fits the needs of my customer; and, he has been running quite well on this
> system with modifications I put in place first more than 10 years ago, and
> another set of changes in 1999 to prepare them for the year 2000
> situation. I will have to change only a small percentage of the programs
> (perhaps 10%), but my modifications will have to work with the remaining
> programs in this package. The documentation supplied by the distributor
> plainly states that if one is going to be modifying the source programs,
> Visual FoxPro Version 6.0 must be used to compile the modified programs.
> The FoxPro runtime routines supplied are from Version 6.0. Thus, my
> search for VFP6.0.
>
> Paul, I did see that item on Ebay, and asked the seller to specifically
> check the documentation for the eligibility of upgrade from FPW2.6. Thank
> you very much for your search and input.
>
> Perhaps my original request was poorly worded. It certainly appears that
> my intelligence, and knowledge of Usenet, does not measure up to that of
> the august posters/readers of this news group.
>
>

Craig
Mon Feb 06 09:49:42 CST 2006

You need to check that. What's included in the Empower program has changed
and MSDN Universal is no longer available.

--
Craig Berntson
MCSD, Visual FoxPro MVP
www.craigberntson.com
Salt Lake City Fox User Group
www.slcfox.org
www.foxcentral.net


"swdev2" <wsanders@dotnetconversions.bob.com> wrote in message
news:u7wzPaqKGHA.208@tk2msftngp13.phx.gbl...
> Heya Lakeside -
>
> The Empower ISV Program includes a 5 license set of MSDN Universal
> Subscription, which contains everything MS puts out, including Visual
> Studio
> 6.0 set, which includes VFP 6.0 .
> There are some qualifications to get listed as an ISV, but its quite easy.
> The price is right too - it's 375 for your year.
> Check it out? www.empowerisv.com
>
>
> I know you're on a quest - I read your trail about SBT. Good Luck with
> it -
> hopefully you'll take the plunge and become an ISV as well.
>
> Mondo Regards [Bill]
> --
> ===================
> William Sanders / EFG VFP / mySql / MS-SQL
> www.efgroup.net/vfpwebhosting
> www.terrafox.net www.viasqlserver.net
>
> <me@privacy.net> wrote in message news:44itaeF2e0vaU2@individual.net...
>> I'm preparing to upgrade an application package that uses Foxpro 2.6 for
>> Windows/DOS, to a newer package that uses Visual Foxpro Version 6.
>>
>> I have an opportunity to buy a used Upgrade version of VFP 6. Would
>> that version consider the old Version 2.6 a qualifying version for
>> upgrade purposes?
>>
>> Thanks for your help.
>>
>> Lakeside
>
>

swdev2
Mon Feb 06 10:00:18 CST 2006

Craig - whoops -
ya - so I missed it, ah?
I'll review tonight and make sure whats a going on, and report back.
thanks for the reality check - I was going on prior information and I now
recall its about 2 years old - but had stayed constant for almost all of
those 2 years (I did check every month until recently).

mondo regards [Bill]

--
===================
William Sanders / EFG VFP / mySql / MS-SQL
www.efgroup.net/vfpwebhosting
www.terrafox.net www.viasqlserver.net

"Craig Berntson" <iamcraig@iamcraigberntson.com> wrote in message
news:#n3QzTzKGHA.4044@TK2MSFTNGP10.phx.gbl...
> You need to check that. What's included in the Empower program has changed
> and MSDN Universal is no longer available.
>
> --
> Craig Berntson
> MCSD, Visual FoxPro MVP
> www.craigberntson.com
> Salt Lake City Fox User Group
> www.slcfox.org
> www.foxcentral.net
>
>
> "swdev2" <wsanders@dotnetconversions.bob.com> wrote in message
> news:u7wzPaqKGHA.208@tk2msftngp13.phx.gbl...
> > Heya Lakeside -
> >
> > The Empower ISV Program includes a 5 license set of MSDN Universal
[snip]

swdev2
Mon Feb 06 12:23:28 CST 2006

Craig - I just got off the phone with two Empower Reps at MSOFT, and they
are checking a lot of things now, as I raised a bunch of issues. Hopefully
I'll hear back with positive answers in the next 48 hours.

Thanks for hitting me over the head about this one - the perceived changes
in the program almost make it a no-go for any VFP developer, and of course I
want it to be the opposite - in fact a 'nice' experience for ANY VFP
developer.

I'll post back here with an update. mondo regards [Bill]

--
===================
William Sanders / EFG VFP / mySql / MS-SQL
www.efgroup.net/vfpwebhosting
www.terrafox.net www.viasqlserver.net

"Craig Berntson" <iamcraig@iamcraigberntson.com> wrote in message
news:#n3QzTzKGHA.4044@TK2MSFTNGP10.phx.gbl...
> You need to check that. What's included in the Empower program has changed
> and MSDN Universal is no longer available.
>
> --
> Craig Berntson
> MCSD, Visual FoxPro MVP
> www.craigberntson.com
> Salt Lake City Fox User Group
> www.slcfox.org
> www.foxcentral.net
>
>
> "swdev2" <wsanders@dotnetconversions.bob.com> wrote in message
> news:u7wzPaqKGHA.208@tk2msftngp13.phx.gbl...
> > Heya Lakeside -
[snip]

Gene
Mon Feb 06 15:47:18 CST 2006

On Sat, 4 Feb 2006 09:20:21 -0800, "Paul Pedersen" <no-reply@swen.com>
wrote:

>If you're going to all the trouble of upgrading a 2.6 app, why not go
>straight to VFP9? Unless you have a good reason for sticking with 6, and I
>can't think of any at the moment, the new features (including stability) of
>9 are well worth the difference in price.

One is which version of Windows is being used. Since Microsoft
does not guarantee that the development environment will work under
Windows 98, I have not upgraded.

What do I tell my boss? VFP9 is better than VFP6? How do I
know? Well, not by my experience, but people have been saying so.
Really! BTW, I need a new OS, too; probably a new computer, too, for
the new OS.

Microsoft has neatly tied a simple software upgrade into a full
system upgrade. My boss is not biting.

[snip]

Sincerely,

Gene Wirchenko

swdev2
Mon Feb 06 17:35:31 CST 2006

Heya Craig -
Official word is that one receives the 'MSDN Premium (Visual Studio Pro)'
bundle - and from there one
can download
VFP 7, VFP 8 and VFP 9.

The listing in the DVD subscription is not complete, but the download area
covers those 3 versions.

NO Version 6 available any more.
bah .
but - hey - thanks for twisting my fingers - I needed to find this out as
well.
regards [Bill]
--
===================
William Sanders / EFG VFP / mySql / MS-SQL
www.efgroup.net/vfpwebhosting
www.terrafox.net www.viasqlserver.net

"Craig Berntson" <iamcraig@iamcraigberntson.com> wrote in message
news:#n3QzTzKGHA.4044@TK2MSFTNGP10.phx.gbl...
> You need to check that. What's included in the Empower program has changed
> and MSDN Universal is no longer available.
>
> --
> Craig Berntson
> MCSD, Visual FoxPro MVP
> www.craigberntson.com
> Salt Lake City Fox User Group
> www.slcfox.org
> www.foxcentral.net
>
>
> "swdev2" <wsanders@dotnetconversions.bob.com> wrote in message
> news:u7wzPaqKGHA.208@tk2msftngp13.phx.gbl...
> > Heya Lakeside -
> >
> > The Empower ISV Program includes a 5 license set of MSDN Universal
> > Subscription, which contains everything MS puts out, including Visual
> > Studio
> > 6.0 set, which includes VFP 6.0 .
> > There are some qualifications to get listed as an ISV, but its quite
easy.
> > The price is right too - it's 375 for your year.
> > Check it out? www.empowerisv.com
> >
> >
> > I know you're on a quest - I read your trail about SBT. Good Luck with
> > it -
> > hopefully you'll take the plunge and become an ISV as well.
> >
> > Mondo Regards [Bill]
> > --
> > ===================
> > William Sanders / EFG VFP / mySql / MS-SQL
> > www.efgroup.net/vfpwebhosting
> > www.terrafox.net www.viasqlserver.net
> >
> > <me@privacy.net> wrote in message news:44itaeF2e0vaU2@individual.net...
> >> I'm preparing to upgrade an application package that uses Foxpro 2.6
for
> >> Windows/DOS, to a newer package that uses Visual Foxpro Version 6.
> >>
> >> I have an opportunity to buy a used Upgrade version of VFP 6. Would
> >> that version consider the old Version 2.6 a qualifying version for
> >> upgrade purposes?
> >>
> >> Thanks for your help.
> >>
> >> Lakeside
> >
> >
>
>

swdev2
Mon Feb 06 20:29:55 CST 2006

Heya Jim -
two things:
1. I gave you the wrong website - its www.empowerforisv.com

2. Craig B (or Mr. B as he is called in the trade) called to my attention
that the sw distribution contents changed. I had a long conference call
with two MSOFT Empower Folks today, and after all is said and done, VFP 6 is
no longer included in the Empower For ISV Program. Versions 7,8 and 9 *ARE*
included, but that doesn't help with that old friend's project. I gave you
bum information, but it wasn't done on purpose - in the previous 'life' of
the program - it was included. My Bad, and My apologies.

hth - regards [Bill]
--
===================
William Sanders / EFG VFP / mySql / MS-SQL
www.efgroup.net/vfpwebhosting
www.terrafox.net www.viasqlserver.net

<me@privacy.net> wrote in message news:44o1uvF34kmrU1@individual.net...
> MANY, MANY thanks, Bill!
>
> I checked out the requirements and I probably can't qualify for a couple
> of reasons. Firstly, I will not be developing anything; rather, I will
> only be modifying an existing package. Secondly, neither my customer
> nor myself have a web page.
>[snip]

me
Mon Feb 06 21:19:04 CST 2006

Paul Pedersen wrote:

> Hmmm, I remember SBT. I did some work with that several years ago, back in
> its 2.6 days.
>
> I didn't know it was a maintenance job; I thought it was conversion. To
> convert a large package like that when only a small change is needed does
> indeed sound like a lot of work for not much benefit.

Paul, I don't really have to convert anything--the customer has bought a
new version of SBT/Vision Point; and, all I have to do is move the
changes I made to their Version 7 over into Version 10. (Please see my
response to "swdev2".)
>
> But if you have to convert the whole thing from 2.6 to VFP, 9 still might be
> the way to go. Unless Sage is still supporting that old version and they
> still insist on VFP6, I wouldn't be overly concerned about that requirement.

Since their website calls SBT a "legacy" product, I'm not holding my
breath on that one.

>
> But if a small change is all that's needed, you might even be better off
> staying with 2.6.

Don't have that option. SBT/Vision Point Version 10 REQUIRES VFP6.0 if
you recompile any of the source programs, which I will have to do.
>
> Don't be overly sensitive. We're all in the same boat here.
>
< < < S N I P > > >

me
Mon Feb 06 21:23:34 CST 2006

swdev2 wrote:

> Heya Jim -
> two things:
> 1. I gave you the wrong website - its www.empowerforisv.com
>
> 2. Craig B (or Mr. B as he is called in the trade) called to my attention
> that the sw distribution contents changed. I had a long conference call
> with two MSOFT Empower Folks today, and after all is said and done, VFP 6 is
> no longer included in the Empower For ISV Program. Versions 7,8 and 9 *ARE*
> included, but that doesn't help with that old friend's project. I gave you
> bum information, but it wasn't done on purpose - in the previous 'life' of
> the program - it was included. My Bad, and My apologies.
>
> hth - regards [Bill]
> --
< < < S N I P > > >

Bill,

No problem--no way I could fault you. Your intentions were good and
honorable. MS just changed the playing field (don't they always?).

I may still pursue that VFP6.0 on Ebay; though the auction has expired,
the seller may relist it (if he didn't sell it).

Best regards,

Jim

Andrew
Tue Feb 07 02:15:00 CST 2006

<me@privacy.net> wrote in message news:44qi5fF3h608U1@individual.net...
> Bill,
>
> No problem--no way I could fault you. Your intentions were good and
> honorable. MS just changed the playing field (don't they always?).
>
> I may still pursue that VFP6.0 on Ebay; though the auction has expired,
> the seller may relist it (if he didn't sell it).

These people are not cheap and I don't know anyone who has actually used
them but they regularly crop up here in response to old version requests.
http://www.emsps.com/oldtools/msfox.htm#vfoxpro6

--
HTH
Andrew Howell

Paul
Tue Feb 07 10:38:50 CST 2006


<me@privacy.net> wrote in message news:44qht2F3g8leU1@individual.net...

>
> Don't have that option. SBT/Vision Point Version 10 REQUIRES VFP6.0 if
> you recompile any of the source programs, which I will have to do.

Oh, I guess I misunderstood.

Perhaps there are existing pieces of Vision Point that you won't be
changing, and those expect that the changed pieces use VFP6. That could
happen, depending on how strongly integrated they all are. OK, now it's
starting to make sense. Maybe something like EBay would be the best source.

OTOH, we've spent enough time on these boards that it almost would have paid
for a new copy!

Is that the newest version of Vision Point?

Paul
Tue Feb 07 10:52:29 CST 2006

While we're on the subject of licenses, can anyone give a definitive answer
regarding whether the MSDN version of VFP can be used to develop commercial
products?

The license text "seems to imply" that MSDN products can be used only for
development and not for production. Yet all their mentions in this matter
also seem to be related to operating systems only. (And Windows Server
understandably seems to be their main concern.)

The only mention I can find of programming tools is this, in the Q&A:

========================
Can I use the Visual Studio product to create an executable file and
distribute this file for sale?

Yes. Applications, utilities, and executables you develop using Visual
Studio, Access, or Office Developer can be distributed to customers
royalty-free, pursuant to the terms of the corresponding End-User License
Agreement (EULA). In addition, there are many redistributable components
included with Visual Studio, which you are welcome to incorporate into your
applications and distribute for free pursuant to the terms of the Visual
Studio EULA.
=====================

FoxPro was briefly part of Visual Studio, but is no longer. Yet VFP is not
mentioned specifically, and like I said, this is the only reference I found
to any programming tools, so it's hard to imagine that it does not apply to
VFP as well. And it very clearly says yes, MSDN programming tools can be
used to develop commercial software.

Comments?

me
Tue Feb 07 22:10:27 CST 2006

Paul Pedersen wrote:

> <me@privacy.net> wrote in message news:44qht2F3g8leU1@individual.net...
>
>
>>Don't have that option. SBT/Vision Point Version 10 REQUIRES VFP6.0 if
>>you recompile any of the source programs, which I will have to do.
>
>
> Oh, I guess I misunderstood.
>
> Perhaps there are existing pieces of Vision Point that you won't be
> changing, and those expect that the changed pieces use VFP6. That could
> happen, depending on how strongly integrated they all are. OK, now it's
> starting to make sense. Maybe something like EBay would be the best source.
>
> OTOH, we've spent enough time on these boards that it almost would have paid
> for a new copy!

Thin you're right about that!
>
> Is that the newest version of Vision Point?
>

I'm not sure, as my customer bought it from an authorized reseller, and
they selected the version together. However, based on what I read on
the Sage web site, and what I remember from a similar discussion with
them last February, I believe it may very well be. It works under XP
Pro, which is what my customer wants. Incidentally, it also works under
W98SE, as I tested the unmodified programs on my testbed system.

>
>

me
Tue Feb 07 22:18:00 CST 2006

Andrew Howell wrote:

< < < S N I P > > >

>
> These people are not cheap and I don't know anyone who has actually used
> them but they regularly crop up here in response to old version requests.
> http://www.emsps.com/oldtools/msfox.htm#vfoxpro6
>

Many thanks, Andrew,

Yup, they are a bit on the high side, but still cheaper than buying the
latest version from M$!

By the way, when looking at the qualifying software for the Upgrade
version of VFP6.0, it says: "Professional Upgrade - This Upgrade can be
installed if you currently have FoxPro 2.5 or later for the PC or Visual
FoxPro 3.0 or later for PC or Mac."

Looks like I may be in business--my customer has FoxPro 2.6 (for
Windows). And, the gentleman who had the auction on Ebay relisted it.

swdev2
Wed Feb 08 15:38:40 CST 2006

Heya Paul -
I've had the MSDN Universal from the Empower ISV Program for a while now,
and though the cobwebs are fuzzy in my wee brain,
I swear that was the intent in the first place - to develop commercial
products.

There is ONE issue with the MSDN Universal - like you can't put more than
one W2003 server up at the developer's site,
and I THINK there is some licensing issue with whether or not one can be
made LIVE on the internet.

But for VFP? NAAAAAAAAAAAAAA.. as long as you aren't using the Academic
Licensing Product from MSDN?
You're fine (or so I thought).
BUT - you want some verbiage out of the licensing statements...
The new MSDN Master EULA lives at
http://msdn.microsoft.com/subscriptions/downloads/EULA.pdf
There's a clause in section 2.a that scares the p|ss out of me - but as I
read further, I find that there is no direct mention
of Visual FoxPro what so ever.

Let me know if you can't see it on the msdn site.
Sorry for the non-answer (at this point).

regards [Bill]

--
===================
William Sanders / EFG VFP / mySql / MS-SQL
www.efgroup.net/vfpwebhosting
www.terrafox.net www.viasqlserver.net

"Paul Pedersen" <no-reply@swen.com> wrote in message
news:OXjGrbALGHA.952@TK2MSFTNGP10.phx.gbl...
> While we're on the subject of licenses, can anyone give a definitive
answer
> regarding whether the MSDN version of VFP can be used to develop
commercial
> products?
>
> The license text "seems to imply" that MSDN products can be used only for
> development and not for production. Yet all their mentions in this matter
> also seem to be related to operating systems only. (And Windows Server
> understandably seems to be their main concern.)
>
> The only mention I can find of programming tools is this, in the Q&A:
>
> ========================
> Can I use the Visual Studio product to create an executable file and
> distribute this file for sale?
>
> Yes. Applications, utilities, and executables you develop using Visual
> Studio, Access, or Office Developer can be distributed to customers
> royalty-free, pursuant to the terms of the corresponding End-User License
> Agreement (EULA). In addition, there are many redistributable components
> included with Visual Studio, which you are welcome to incorporate into
your
> applications and distribute for free pursuant to the terms of the Visual
> Studio EULA.
> =====================
>
> FoxPro was briefly part of Visual Studio, but is no longer. Yet VFP is not
> mentioned specifically, and like I said, this is the only reference I
found
> to any programming tools, so it's hard to imagine that it does not apply
to
> VFP as well. And it very clearly says yes, MSDN programming tools can be
> used to develop commercial software.
>
> Comments?
>
>
>
>

Paul
Wed Feb 08 20:20:55 CST 2006


"swdev2" <wsanders@dotnetconversions.bob.com> wrote in message
news:Of7v0fPLGHA.2704@TK2MSFTNGP15.phx.gbl...
> Heya Paul -
> I've had the MSDN Universal from the Empower ISV Program for a while now,
> and though the cobwebs are fuzzy in my wee brain,
> I swear that was the intent in the first place - to develop commercial
> products.

Mine is (was - it's expired now) Professional. But the license in this
respect is the same, I think.



> There is ONE issue with the MSDN Universal - like you can't put more than
> one W2003 server up at the developer's site,
> and I THINK there is some licensing issue with whether or not one can be
> made LIVE on the internet.

Yes, they're concerned about Windows Server.



> But for VFP? NAAAAAAAAAAAAAA.. as long as you aren't using the Academic
> Licensing Product from MSDN?

No, definitely not Academic.



> You're fine (or so I thought).
> BUT - you want some verbiage out of the licensing statements...
> The new MSDN Master EULA lives at
> http://msdn.microsoft.com/subscriptions/downloads/EULA.pdf
> There's a clause in section 2.a that scares the p|ss out of me

That's the part I mentioned first. Yet my second reference, clearly giving
permission, was taken directly the MSDN site.


- but as I
> read further, I find that there is no direct mention
> of Visual FoxPro what so ever.
>
> Let me know if you can't see it on the msdn site.
> Sorry for the non-answer (at this point).

A non-answer is all I've been able to get, unfortunately. Well, I did run
into someone who claimed to have the answer, but I was not convinced.

Perhaps the lawyers deliberately made it ambiguous, trying to give
themselves work in future disputes.

But my feeling is, that one section "Can I develop applications... Yes" is
pretty clear.