>If you want to use VFP as a dataprovider for data that needs to be created the above is a showstopper.
Right,
And, if you want to migrate a VFP/DBC/BDF codebase to .Net in a Feature driven way provided parallel features that use the same data, with the goal of replacing the VFP app with a .Net app.. then you need the speed and power of the VFP engine in the provider so you can do record based processing, etc.
After you are 100% .Net code, then you can talk about upsizing the data store to a real db server.
See VistaDb... it has higly performant row based and xBase like features. The VFP provider should be similar but use DBC/DBF files.
And, all VFP engine stuff should be supported like Triggers, Rules, DB Events, etc.
BOb
Précédent
Répondre
Voir le fil de ce thread
Voir le fil de ce thread à partir de ce message seulement
Voir tous les messages de ce thread
Voir tous les messages de ce thread à partir de ce message seulement