General information
Category:
Database DAO/RDO/ODBC/ADO
>Hey folks. I could use a few opinions. A colleague and I are developing an app that runs a series of exports from a SQL Server back-end. Our general object design uses a data-connection object, which is responsible for establishing a connection, and retrieving a recordset (sometimes sproc-based, sometimes a SQL Select statement, sometimes a view, etc.). From there, the resulting ADO recordset is passed to an entirely separate data-manipulation class, (instantiated as a hook-object of sorts, responsible for any additional manipulation that might be required -- formatting changes, or further parsing down the record set)
>
>Here's my question - is there an overriding reason to code the data-connection class in either VB *or* VFP? This app will definitely have components of both languages anyway, so run-times, etc., are not an issue. Is VB (or VFP) more stable as an ADO-connection layer? Is VFP (or VB) quicker at the pure connection piece of it? Remember, this data conenction class is responsible for establishing a connection and returning a recordset - nothing else. No data-processing involved in this later.
>
>I am leaning toward VB because I have a hunch that the resulting object will be smaller than a similar VFP object; does anyone else have an informed opinion to add to the mix for me?
>
>Thanks in advance.
I think object instantiation in VB would be faster if you are not running objects within MTS and if you take advantage of early binding.
Otherwise, I don't see great difference working with ADO with VFP or VB.
Previous
Next
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only