I am planning to keep the front end scripts on an NT box, but would like to use msql on the back-end instead of sql server. Will there be any issues associated with that?
To be honest, I'm not sure. Other than hearing about mSql, I don't really know much about it. I've never used the product. Try it and let me know how it goes.
I would guess at a very minimum you would need to change the CreateDatabaseConnection function in the class.asp file to get it to connect to your mSql DB. Other than that it should be just the general sql syntax, typically this is not identical from DB to DB.
If there is enough demand for an alternate db, I would be willing to add it. However, I would have to say at this point, support for mySql is definately ahead of mSql to be added in the future.
msql
To be honest, I'm not sure. Other than hearing about mSql, I don't really know much about it. I've never used the product. Try it and let me know how it goes.
I would guess at a very minimum you would need to change the CreateDatabaseConnection function in the class.asp file to get it to connect to your mSql DB. Other than that it should be just the general sql syntax, typically this is not identical from DB to DB.
If there is enough demand for an alternate db, I would be willing to add it. However, I would have to say at this point, support for mySql is definately ahead of mSql to be added in the future.
~Chad