Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Has anybody noticed the significance ... ?.

Status
Not open for further replies.

Mike Lewis

Programmer
Jan 10, 2003
17,505
Scotland
Has anybody noticed the significance of the date: July 2015?

It is exactly 20 years since Visual FoxPro was released. That's right. VFP 3.0 (the first version of Visual FoxPro) come out in July 1995 - just a few weeks before Windows 95.

How many of us were around at the time?

Mike


__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads
 
dBASE II has been mentioned a couple of times in this thread. It set me thinking about some of the limitations that we had to work under in those days:

- Only two work areas (primary and secondary). In other words, only two tables (we called them databases in those days) could be open at one time. It's amazing what hoops we had to jump through to live with that restriction.

- The only data types were character, numeric and logical. So, no dates or datetimes, and certainly no binary, floating point, integer, general, etc.

- Strings were limited to 254 characters. So no memos or other ways of storing long pieces of text.

- A maximum of 64 variables at any one time.

- No SEEK command or function. The equivalent was FIND (which is still present in the language). This worked like the SEEK command, except that you had to specify the searched-for terms as a literal. In other words, instead of this:

[tt]lcSearch = "ALKFI"
SEEK lcSearch[/tt]

you had to do this:

[tt]FIND ALFKI[/tt]

Fortunately, we had macros, so that wasn't as big a problem as you might think.

But still, dBASE II was a big advance on its predecessor, which was called Vulcan (and which was never commercially exploited). That had limitations of its own:

- No indexes. All searches were sequential (aka brute force).

- No cursor-positioning commands, such @/SAY. All input and output had to be done via a command-line interface.

I'm sure there were other limitations, but those are the ones I can remember. Perhaps someone will remind me if I've misssd any.

Mike

__________________________________
Mike Lewis (Edinburgh, Scotland)

Visual FoxPro articles, tips and downloads
 
Speaking of limitations, allow me me to reminisce a little here. Even with the advent of multiple work areas or file handles in (I believe) dBaseIII+ and FoxBase, as I recall there was still a limit of 10 file handles. There was some hoop jumping to even use that few tables and their associated indexes. Who besides me was constantly reindexing because they forgot to open all the indexes created for a particular table before updating the table? This of course before Fox opened them automatically using compound indexes.


-Dave Summers-
[cheers]
Even more Fox stuff at:
 
Same here: dbase III+, Foxbase, Foxpro, Clipper...

Where do we go from here though? What can you recommend as the best choice for the future of xBase?



Thanks,

Michael42

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top