Yo, reading my post again, it seems that Im not beeing too much polite...  about:   if it's easy, do it... what i mean was... íf that can be done in 10 minutes (those easy kind of things), please do it, (when u guys have time)... Thanks Ben and Trent..

Will do, Ricardo

Hi put me on the list of 10-20 users about VistaBD.

I suggest Advantage because it can handle DBF files which means a VFP developer could build net apps that access VFP data while older applications still access the same data. This creates a nice migration path for such developers.

Here in Brazil we are having the same issue on our clients.. if it's easy to do, please do it...    

What you'll need to do is create a new class, I'd probably call it VistaDbDataSourceItem, and have it inherit from MicroFour.StrataFrame.Data.DbDataSourceItem.  There are a few methods in there that must be overriden to provide functionality specific to VistaDb.  My recommendation is to use the source code for the SqlDataSourceItem class (or one of the others such as AccessDataSourceItem, or OracleDataSourceItem) as a template for your VistaDbDataSourceItem class.  Once you've created the class, simply add an instance of the class to the DataLayer.DataSources collection within the AppMain.vb (or program.cs) file and the SF Framework will treat it as just another data source (the business objects won't even know the difference).

I would also add my vote to VistaDb as well. In the mean time it would be helpful to understand what is involved in doing this myself as you suggested was possible and quite straightforward.

Yes, we have had several users mention VistaDB as well, and both of those databases have provider implementations that utilize the base classes from the System.Data.Common namespace, so implementing their native providers would be straightforward. However, we have not had any users directly request either of them, so until we do, we will probably not create an implementation for either. If one user wants VistaDB, he can create his own DbDataSourceItem class for use with StrataFrame, but if 10-20 users want to use VistaDB, it would be cost effective for us to create the class and include it with StrataFrame. So, right now the demand is just not there; once it is, we'll be on top of it.

I see from the documentation that you have support for several database servers. I would like to add a suggestion for two other database servers: Advantage Database Server, VistaDB.



I suggest Advantage because it can handle DBF files which means a VFP developer could build net apps that access VFP data while older applications still access the same data. This creates a nice migration path for such developers.



Regards,

Simon