Agree.
There are too much VB jobs, but too too less VFP jobs in HONG KONG too.

Toms

> >
> > FOXPRO IS NOT DEAD!
> >
> > ;-)
> >
> > Those lamers just want to defend themselves to what they know and protect what they don't
> > know about. VB... ;-) well thats a very good language, yet FOXPRO is better in some areas
> > specially DATA. I agree with that!
> >
> > The battle here is this (fer example) ...
> >
> > 1. can foxpro do the (RI) Referential Integrity thing??? ;-)
> > well if you say ull be using a .DBF that may not work. and if you want to make
> > solutions then you have to CODE (that sux).
> >
> > Now, SQL Server comes in with Referential Integrity, database triggers etc.
> >
> > Most lamers think of this -> if you are using FOXPRO you are using DBF... ;-)
> >
> > nah... think again
> >
> > 2. can foxpro do the "SECURITY" thing???
> > if you have a .DBF that may not work... and if you wanna make that possible
> > you have to code! n what... ENCRYPTION or maybe DBFLOCK... (not in multiusermode)
> >
> > Now, SQL Server comes in again... for better / stronger SECURITY
> >
> > 3. how about DATABASE INTEGRITY AND CONSISTENCY???
> >
> > Hey! this argument is endless. Those lamers doesn't know the difference of what a
> > database, a table, a DBMS, or a RDBMS, client-server, multi-tier, multi-thread, sockets,
> > dataports, DDE, data sharing, perhaps an IOCTL or much more the language itself.
> >
> > using a SEEK / LOCATE / FINDFIRST / FINDPREV / APPEND / INSERT INTO / UPDATE /
> > DELETE (or whatever the hell it is) doesnt prove that a software or language is inefficient.
> >
> > 4. try this at home kids. this is simply ASSEMBLY... ;-)
> >
> > a. run MSDOS prompt
> > b. type -> C:\<br />> > c. type -> COPY CON RESET.COM
> > d. type the number HOLDING the alt-keys -> ALT+205 ALT+25
> > e. then press -> CTRL+Z
> >
> > voila you have a RESET.COM -> (now this code rulez!!!) it is simly a RESET program
> > for DOS. type RESET.COM and your DOSBOX flies away... now thats kewl ;-)
> >
> > in ASSEMBLY,
> >
> > a. run MSDOS prompt
> > b. type -> DEBUG.COM {press enter}
> > c. type -> n RESET.COM {press enter}
> > d. type -> a 100 {press enter}
> > e. type -> INT 19 {press enter}
> > f. type -> RCX {press enter}
> > g. type -> 02 {press enter}
> > h. type -> w {press enter}
> >
> > and voila, its just the same... INT 19 means System Reset in ASM
> >
> > well. my point here is that I was able to make a reset program WITHOUT ANY DAMN LANGUAGE.
> > just COPY CON!
> >
> > ----------------------------
> >
> > WELL, THE POWER OF A LANGUAGE IS USELESS IF IT IS NOT HARNESSED BY THE
> > ONE USING IT. ;-)
> >
> > -Mz DarkReligion----
>
>
>
>
>
>
> Ya know Guys I love FoxPro… I have used it in every job I have ever had for the last 11 Years.
>
> Now the time has come when I can no longer find work as a Foxpro programmer in my home state… In talking with headhunters it turns out that there are close to 50 to 100 Foxpro work hungry programmers to every 1 job!
>
> I wish I could say the “FoxPro” was the language of choice… But its just not…
>
> The worst thing is that now most Foxpro jobs are along the lines of… “Support this old Foxpro App… while we put in its replacement! (AkA my last job).
>
> I want Foxpro to be the “King of the Hill” But do the math your self!
>
> On Monster.com as of September 6, 2003 there are 119 total Foxpro jobs as to 2621 VB jobs… And I hate to say this a lot of the 119 Foxpro jobs are not “True” Foxpro Jobs…
>
> I am looking now to get out of programming all together…
>
> CraigP