Hehe, yeah, it can do plenty right now

Great news!  Can't wait for the update.  I guess I have a busy week infront of me trying to find out all the cool stuff the framework can ALREADY do.

Scott

Scott,



We're in the process of finishing up our Oracle & OLE DB support. Yes, we will have the functionality to support more than one simultaneous data source (we had to add it out of necessity for Practice Studio as the old version is on FoxPro databases and the new modules are SQL Server). You don't have the functionality right now, but it should be finished by the end of next week. You'll set the connection key/index on the business object to tell it what data source to use.



On the issue of being able to create the proper parameter for the proper data source, yes, that is feasable, as the business object will know it's data source type and I'll look into adding that functionality

I want to be able to support multiple backend datasources, like SQL Server or OLE DB(FoxPro tables).  I can see that by changing the connection string for the whole application the system will be looking at a different datasource.  The two main questions that I have are:

One - will business objects that are developed using SQL be able to "switch" to using OLE DB to access data from that source?

Two - In the documentation there is a lot of examples where a SQLCommand object is created and parameters are added.  Is there a way that this can be done so that the system can create the appropriate command object (based on the current connection type) and make the calls to add the parameters internally?

Thanks for any input and have a Happy Thanksgiving!