Replace FoxPro with dotNet and SQL Server

This seems to be Microsoft's preferred approach and they've introduced Linq (Language Integrated Query) into dotNet. Linq does not use SQL syntax and in some ways I wish that they'd chosen to use the commands that are familiar to me from FoxPro. I have to accept though that FoxPro commands are idiosyncratic and inconsistent. They make sense to me because I've grown up with them but perhaps it is time to create a new language that will be easier for newcomers to learn.

The introduction of SQL Server Express takes a lot of the complexity out of database management. It's still not as easy as the flexible - some might say slapdash - approach of FoxPro but SQL Server Express is a good tool for a small database with simple needs.

As with the Access approach, this solution does not properly replace the interactive features of FoxPro. There is however always the option migrating your main system to dotNet but keeping FoxPro on yor desktop with a link into SQL Server for when you need to take a closer look at the data.

MS Access technical tips

Visual FoxPro technical tips

General Tips

 

More tips from Alvechurch Data

How can we replace FoxPro

What will replace FoxPro when support ceases in 2015

Read More

Continue to use Microsoft FoxPro

Continue using your FoxPro database until 2020. There's no need to replace it yet.

Read More

Replace a FoxPro database with Micosoft Access

Microsoft Access is a good replacement for a small FoxPro database

Read More

Wait for Microsofts FoxPro strategy

Keep using Visual FoxPro and wait for Microsoft's strategy to become clear.

Read More