in the end depending on the OP's budget they may be better off just buying ms sql server. it's not THAT expensive. it all depends on their budget and requirements. if i was at a company which would stand to lose money because our HR/accounting/payroll system is not running, i would gladly pay for MS SQL server if it meant i could have a system right away, rather than sit around waiting for some schmoes to figure out this "free" stuff.
On 4/26/06, Andre John Cruz <[EMAIL PROTECTED]> wrote:
the more difficult part of this is that the database access classes in .NET are specific to a particular database server type. For example, the class SqlConnection in the System.Data.SqlClient namespace is for MS SQL Server only, as well as its other classes SqlCommand, SqlDataReader, SqlDataAdapter, etc. That means if you reference these class names directly, you'll be in for a lot of search-n-replace in the code (not to mention that you still have to test it extensively afterwards).
_________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
