I'm wondering if creating interfaces in VC++,populating
list boxes and grids is similar and as easy and as
flexable as VFP.

I'm thinking of developing the same app I developed with
VFP in VC++ so I can say I did it in VC++ as well.

Are the VC++ controls similar to VFP controls with
methods and properties etc. Are classes just as easy to
work with?

Thanks in advance

Re: VFP to VC++ by frederic

frederic
Thu Nov 27 12:50:18 CST 2003

Bonjour Jack


For a start and just to have an idea of the task, have a look at MSDN and
code snippets... then you'll be glad to stay on VFP, even if VC++ allows you
more control on windows controls ...

just my .02

Fred


Pour mémoire, tu nous as écrit :

> I'm wondering if creating interfaces in VC++,populating
> list boxes and grids is similar and as easy and as
> flexable as VFP.
>
> I'm thinking of developing the same app I developed with
> VFP in VC++ so I can say I did it in VC++ as well.
>
> Are the VC++ controls similar to VFP controls with
> methods and properties etc. Are classes just as easy to
> work with?
>
> Thanks in advance


Re: VFP to VC++ by Alan

Alan
Fri Nov 28 03:08:03 CST 2003

"Jack" <anonymous@discussions.microsoft.com> wrote in news:017e01c3b50f
$98018840$a101280a@phx.gbl:

>
> I'm wondering if creating interfaces in VC++,populating
> list boxes and grids is similar and as easy and as
> flexable as VFP.

Erm .. not really. Yes, you can use the MFC and design nice forms and so
on but under the hood it's really a lot more complex. Also, after VFP
you'll find that something like opening a table and populating controls is
a lot more involved.



>
> I'm thinking of developing the same app I developed with
> VFP in VC++ so I can say I did it in VC++ as well.
>
> Are the VC++ controls similar to VFP controls with
> methods and properties etc. Are classes just as easy to
> work with?

Again ... not really IMO. In C you have to think of constructors,
destructors and a whole lot of other stuff. Think of VFP as being 'OOP
lite' and as a much higher-level RAD tool than C. Actually, I'd do it in
C# before I'd do it in C++.



--
* Need help running those old FoxPro / xBase apps on modern systems ?
* http://www.hentzenwerke.com/catalogpricelists/painlesse.htm

Re: VFP to VC++ by vp

vp
Fri Nov 28 10:23:32 CST 2003


Thanks Alan, I'm going to look into C#.


>-----Original Message-----
>"Jack" <anonymous@discussions.microsoft.com> wrote in
news:017e01c3b50f
>$98018840$a101280a@phx.gbl:
>
>>
>> I'm wondering if creating interfaces in
VC++,populating
>> list boxes and grids is similar and as easy and as
>> flexable as VFP.
>
>Erm .. not really. Yes, you can use the MFC and design
nice forms and so
>on but under the hood it's really a lot more complex.
Also, after VFP
>you'll find that something like opening a table and
populating controls is
>a lot more involved.
>
>
>
>>
>> I'm thinking of developing the same app I developed
with
>> VFP in VC++ so I can say I did it in VC++ as well.
>>
>> Are the VC++ controls similar to VFP controls with
>> methods and properties etc. Are classes just as easy
to
>> work with?
>
>Again ... not really IMO. In C you have to think of
constructors,
>destructors and a whole lot of other stuff. Think of VFP
as being 'OOP
>lite' and as a much higher-level RAD tool than C.
Actually, I'd do it in
>C# before I'd do it in C++.
>
>
>
>--
>* Need help running those old FoxPro / xBase apps on
modern systems ?
>*
http://www.hentzenwerke.com/catalogpricelists/painlesse.ht
m
>.
>

Re: VFP to VC++ by Jack

Jack
Fri Nov 28 10:25:33 CST 2003


Your .02 is appreciated.
Thanks Fred


>-----Original Message-----
>Bonjour Jack
>
>
>For a start and just to have an idea of the task, have a=20
look at MSDN and
>code snippets... then you'll be glad to stay on VFP,=20
even if VC++ allows you
>more control on windows controls ...
>
>just my .02
>
>Fred
>
>
>Pour m=E9moire, tu nous as =E9crit :
>
>> I'm wondering if creating interfaces in VC++,populating
>> list boxes and grids is similar and as easy and as
>> flexable as VFP.
>>
>> I'm thinking of developing the same app I developed=20
with
>> VFP in VC++ so I can say I did it in VC++ as well.
>>
>> Are the VC++ controls similar to VFP controls with
>> methods and properties etc. Are classes just as easy=20
to
>> work with?
>>
>> Thanks in advance
>
>.
>

Re: VFP to VC++ by Jack

Jack
Fri Nov 28 12:14:56 CST 2003


Hi Alan,
What if I use SQL/views to poplulate controls, grids and
access/save data. Would it be any easier? Are the
controls similar to VFP? Is C# OPP lite and RAD like VFP?


>-----Original Message-----
>"Jack" <anonymous@discussions.microsoft.com> wrote in
news:017e01c3b50f
>$98018840$a101280a@phx.gbl:
>
>>
>> I'm wondering if creating interfaces in
VC++,populating
>> list boxes and grids is similar and as easy and as
>> flexable as VFP.
>
>Erm .. not really. Yes, you can use the MFC and design
nice forms and so
>on but under the hood it's really a lot more complex.
Also, after VFP
>you'll find that something like opening a table and
populating controls is
>a lot more involved.
>
>
>
>>
>> I'm thinking of developing the same app I developed
with
>> VFP in VC++ so I can say I did it in VC++ as well.
>>
>> Are the VC++ controls similar to VFP controls with
>> methods and properties etc. Are classes just as easy
to
>> work with?
>
>Again ... not really IMO. In C you have to think of
constructors,
>destructors and a whole lot of other stuff. Think of VFP
as being 'OOP
>lite' and as a much higher-level RAD tool than C.
Actually, I'd do it in
>C# before I'd do it in C++.
>
>
>
>--
>* Need help running those old FoxPro / xBase apps on
modern systems ?
>*
http://www.hentzenwerke.com/catalogpricelists/painlesse.ht
m
>.
>

Re: VFP to VC++ by Alan

Alan
Mon Dec 01 03:28:45 CST 2003

"Jack" <anonymous@discussions.microsoft.com> wrote in news:8f0c01c3b5db
$8739e710$a601280a@phx.gbl:

>
> Hi Alan,
> What if I use SQL/views to poplulate controls, grids and
> access/save data. Would it be any easier? Are the
> controls similar to VFP? Is C# OPP lite and RAD like VFP?

Again, might be easier but nothing will be as easy as it is in VFP! The
controls are broadly similar, i.e. a Textbox will have much the same
properties and events as a VFP textbox.

C# has C-like syntax but is much simpler - a lot of the tedium of pure C
like pointers, memory management and so on is removed. To me it's like C
with all the annoying crap you have to do to get anything working removed.
Also, ADO.Net is probably easier for data access.

--
* Need help running those old FoxPro / xBase apps on modern systems ?
* http://www.hentzenwerke.com/catalogpricelists/painlesse.htm

Re: VFP to VC++ by Balboos

Balboos
Mon Dec 01 20:16:43 CST 2003

Like all things, in programming it is also true: one exchanges
convenience for control. One driving force of going to a lower level
language is that one finds in the higher level language one "can't get
there from here". Or the path is very cumbersome and inefficient.

A chain saw is better at cutting down trees, and a hand saw will take a
much longer time to do the job. But then, when you need to cut a board
to size, the chain saw may lose its appeal.

As for C# - it appears to be an unnecessary step - almost redundant with
Visual Basic (or will it truly replace it?). An it sure looks an awful
lot like JAVA.

Excuse me for being cynical, but MS would have better served its
customers by using the C# development crew to debug Windows !

Other's opinions will vary. My view may be distorted by having found,
in the past, Assembly Language the correct solution at times.

Balboos

Alan B wrote:
> "Jack" <anonymous@discussions.microsoft.com> wrote in news:8f0c01c3b5db
> $8739e710$a601280a@phx.gbl:
>
>
>>Hi Alan,
>>What if I use SQL/views to poplulate controls, grids and
>>access/save data. Would it be any easier? Are the
>>controls similar to VFP? Is C# OPP lite and RAD like VFP?
>
>
> Again, might be easier but nothing will be as easy as it is in VFP! The
> controls are broadly similar, i.e. a Textbox will have much the same
> properties and events as a VFP textbox.
>
> C# has C-like syntax but is much simpler - a lot of the tedium of pure C
> like pointers, memory management and so on is removed. To me it's like C
> with all the annoying crap you have to do to get anything working removed.
> Also, ADO.Net is probably easier for data access.
>


Re: VFP to VC++ by Alan

Alan
Wed Dec 03 08:13:08 CST 2003

Balboos <balboos@masonicbrother.com.No.Spam> wrote in
news:fCSyb.1134$9J6.142842@news4.srv.hcvlny.cv.net:


> As for C# - it appears to be an unnecessary step - almost redundant
> with Visual Basic (or will it truly replace it?). An it sure looks an
> awful lot like JAVA.

Yes it's very like Java.


--
* Need help running those old FoxPro / xBase apps on modern systems ?
* http://www.hentzenwerke.com/catalogpricelists/painlesse.htm