Fox
-
I have to use a program that was written in FoxPro here at work, and I was wondering what other people think of FoxPro? Also, does anyone know if it's going to be part of the whole .NET, CLR thing? "das leid schlaft in der maschine" -Einstürzende Neubauten Daniel
-
I have to use a program that was written in FoxPro here at work, and I was wondering what other people think of FoxPro? Also, does anyone know if it's going to be part of the whole .NET, CLR thing? "das leid schlaft in der maschine" -Einstürzende Neubauten Daniel
Fox is not part of the ".NET, CLR thing", but there is a new version that's going to be out "real soon now"...
-
I have to use a program that was written in FoxPro here at work, and I was wondering what other people think of FoxPro? Also, does anyone know if it's going to be part of the whole .NET, CLR thing? "das leid schlaft in der maschine" -Einstürzende Neubauten Daniel
VS.NET beta 1 includes Visual FoxPro. It was funny hearing Don Box doing a presentation on VS where he remarked 'and you'll notice in my installation of VS that I've done what every other developer does when installing it - I've removed FoxPro' cheers, Chris Maunder
-
VS.NET beta 1 includes Visual FoxPro. It was funny hearing Don Box doing a presentation on VS where he remarked 'and you'll notice in my installation of VS that I've done what every other developer does when installing it - I've removed FoxPro' cheers, Chris Maunder
LOL! That's just too funny! I've never had Fox installed, but if it's as clumsy to program with as it is to use the apps developed with it I can see why no one else wants to use it. I can't help wondering why are all the edit boxes are filled with space characters? And all the programs I've seen are dialog base -- but hosted in a MainFrame. What's the point of that? The list goes on. I get the impression that fox is VB's retarded little brother. "das leid schlaft in der maschine" -Einstürzende Neubauten Daniel
-
LOL! That's just too funny! I've never had Fox installed, but if it's as clumsy to program with as it is to use the apps developed with it I can see why no one else wants to use it. I can't help wondering why are all the edit boxes are filled with space characters? And all the programs I've seen are dialog base -- but hosted in a MainFrame. What's the point of that? The list goes on. I get the impression that fox is VB's retarded little brother. "das leid schlaft in der maschine" -Einstürzende Neubauten Daniel
-
LOL! That's just too funny! I've never had Fox installed, but if it's as clumsy to program with as it is to use the apps developed with it I can see why no one else wants to use it. I can't help wondering why are all the edit boxes are filled with space characters? And all the programs I've seen are dialog base -- but hosted in a MainFrame. What's the point of that? The list goes on. I get the impression that fox is VB's retarded little brother. "das leid schlaft in der maschine" -Einstürzende Neubauten Daniel
>I get the impression that fox is VB's retarded little brother ROFL. I tried to play around with Fox Pro, for curiosity reasons, and I cannot see any use for it. It seems like it is placed somewhere in between VB and Access, glued together with a Windows 3.x interface. Does anybody use it? Christian Skovdal Andersen
-
>I get the impression that fox is VB's retarded little brother ROFL. I tried to play around with Fox Pro, for curiosity reasons, and I cannot see any use for it. It seems like it is placed somewhere in between VB and Access, glued together with a Windows 3.x interface. Does anybody use it? Christian Skovdal Andersen
I used FoxPro years ago before Microsoft bought it... I think it was one of the original Mac database tools. I believe it competed with Clipper for smaller scale, pc-based database application programming (in that you could produce an exe of sorts and run it on a client machine without having to have FoxPro installed). FoxPro had "Rushmore Technology" that basically made it faster than anything out there, circa 1992-3. Microsoft bought it for the Rushmore technology and implemented it in Access 2.0, but discovered, much to their horror, that they couldn't just kill off FoxPro once they had the technology, as the legions of die-hard FoxPro developers and users complained. I think Microsoft has been wanting to put it out of their misery for years, every new version that comes out is reportedly the "last version", but it keeps chugging along. I had a couple of coworkers who were rabid FoxPro users. They would laugh off Access as a joke and say that they could write apps entirely in FoxPro that would put any server-based RDMS to shame. I have to admit, having the Command box is a pretty cool idea ... if you know exactly what you want to, it's a lot simpler to type it in than go on a click-fest. Pretty much everything db-related in FoxPro can be done in the command box, and I gather that's how a lot of these apps got written. This makes me wonder if other pc-only database programs like Clipper or even dBase still exist. Perhaps someone is still working on a copy of dBase III+ or IV out there?;P