Philip Arnold - ASP wrote: > > It's probably better to use mySQL anyways as if you ever have to upgrade > the number of users, then you don't have to do anything - with Access > you'd have to re-write to get it working with a real database engine > once you increase the number of users
It is probably better to use Access anyways as if you ever have to use subqueries, then you don't have to do anything - with MySQL you'd have to rewrite to get it working once you need subqueries or real foreign keys. It is just as easy to turn the argments. Could everybody please open his/hers eyes and see that there is no final answer to the question. One RDBMS is better at doing thing A, another one at doing thing B and another one at doing thing C. This list could perhaps agree on a recommendation for a certain RDBMS, but first we need to have defined whether somebody needs to do thing A, B or C. There are plenty of arguments to use one RDBMS over another one. But there is no definite answer to the question which is the best. It all depends on your requirements and resources. Learn SQL that will work with *every* RDBMS. Learn what the strong points of each RDBMS are. Learn in which case *not* to use a certain RDBMS (probably the most important part). And please open your eyes for all the other solutions apart from Access and MySQL that are available. Jochem ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
