This project is read-only.

38209 Data Explorer 3


Note: this project has moved to GitHub:

Project Manager: Rick Schummer

The Data Explorer lets you examine data and components in Visual FoxPro databases, SQL Server databases, VFP free tables, or any other ODBC or OLE DB compliant database via an ADO connection. It can run as a task pane or as a standalone tool. Those familiar with SQL Server's Management Studio or Visual Studio's Server Explorer immediately notice some similarities, but this tool works with all kinds of data, is completely integrated in the Visual FoxPro IDE, and is extensible in true VFP tradition.

Version 3 extends on the functionality provided by the Data Explorer released with Sedna. Specifically:
  • Export/Import of Data Explorer features to share with others
  • BROWSE for SQL Server with data update capability
  • Toggling the Dock State of the Data Explorer form when standalone
  • New LIST STRU off the shortcut menu
  • New connection type for Directory shows list of all DBFs in a folder
  • Corrected bug in Display Show Plan option added to Sedna version of Data Explorer
  • VFPX Repository (

New file called ChangeLog.TXT included in the project and source with latest changes in each release.

vfpxreleasesmall.png Latest Release of Data Explorer 3

Last edited Aug 24, 2017 at 10:33 PM by DougHennig, version 10


billand88 Jun 24, 2014 at 10:21 PM 
Version 3.03

Run Data Explorer and Select the Add Connection button. Assume there are SQL Server instances out there (probably not relevant, but JIC...). For the server name in the SQL Connection Properties, type in "Junk", assuming there is NOT a server out there named "Junk". Press the OK button.

Click on the associated + icon for "Junk". Eventually you will get a Connect As dialog.

Grab the title bar for the Connect As dialog and drag it all over your Data Explorer window. Now it looks like you played Solitaire and won, and the cards are tumbling down.

I've seen this before and (without looking at source) there's some sort of LockScreen problem.

stanlyn Dec 22, 2012 at 3:55 AM 
Hi Rick,
I cannot connect to a SQL Server 2012 machine using a non-standard port number (a port number other than 1433). I'm using sa with sa_password as credentials and have tried using both a comma and a colon as the server name/port number delimiter, as in
SQL2012:1111 or SQL2012,1111 The comma works in both the Management Studio and ODBC Data Sources. None of these works in DataExplorer3...

Am I missing something here?