How did VB 1 access data?

[orafan2]

Hi,

I am developing a Website dedicated to VB. One of the pages is dedicated to the history of Visual Basic. I want to find out how VB 1 stored data? I know that VB 1 was released in March/1991. What was it's native file system? Was it xBase format files such as .DBF etc.? It cannot be MS Access because MS Access was released in December 1992. Can anybody help me out here.

REgards,
Orafan2

[Jerry Grant]

From MSDN

Visual Basic 1.0 didn't have built-in data access (unless you count low-level file I/O). Even so, with the aid of third-party tools, a large percentage of VB1-authored programs were database applications. Even then, developers who needed to write custom database applications embraced VB. And each successive version of Visual Basic has upped the database ante: VB2 introduced ODBC data access, VB3 gave us the Jet Database Engine 1.1, and the Visual Basic Compatibility Layer (VBCL) let VB3 work with Jet 2.0. In the world of 32-bit tools, VB4 provided us with non-Jet data access in the form of Remote Data Objects (RDO), and VB5 gave us the UserConnection Designer, the T-SQL Debugger, RDO 2.0, and the Visual Database Tools (VDT), which ran under the Developer Studio IDE. Microsoft's release of ActiveX Data Objects (ADO) 1.0 and 1.5 gave VB developers even more data-access options.

[orafan2]

Hi Jerry,
Thanks for the reply. I learnt a lot. But tell me this. With VB 1 what were these 3rd party tools? You say that most of the VB 1 applications were database applications. IF this is so there must have been a popular file system such as .DBF etc. Also with VB2 and ODBC which database access were possible? Because VB2 debuted in Nov/1992 (Check out this VB history page
http://www.johnsmiley.com/visualbasic/vbhistory.htm
). MS Acces also first shipped in Nov/1992. So was VB2 accessing MS Access through ODBC? How about xBase (i.e. .DBF ) files?

Thanks & REgards,

OF2

[Jerry Grant]

Sorry orafan2,
This was just something I found in MSDN!
I started with VB3, and I don't have anything else. So you will have to ask elswhere!
Have you contacted Microsoft, as I'm sure they will be only too pleased to help out.