Mwp.Reid at Queens-Belfast.AC.UK
Mwp.Reid at Queens-Belfast.AC.UK
Sat Mar 15 02:22:01 CST 2003
I didnt say that I said Whats the application? How many users? etc all the usual stuff. Choice depends on a lot of things. Does the customer need the power of SQL Server right now or will they need it very soon? If they are already using SQL Server I would go Access XP and ADPs. If I have to develop an interface to SQL Server Its an ADP. End of day it has to be the right tool for the job. Martin > I don't necessarily agree with Martin -- just because you have SQL > Server > isn't a good reason to go .adp, BUT if you have all the pieces and it's > just > a question of choice, why not? > > Susan H. > > > > Chris > > > > Whats the application? How many users? etc all the usual stuff. > Choice > depends > > on a lot of things. Does the customer need the power of SQL Server > right > now > > or will they need it very soon? If they are already using SQL Server > I > would > > go Access XP and ADPs. > > > > > > Martin > > > > > > > > _______________________________________________ > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > > > > > > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com > > > > _______________________________________________ > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >