Databases used

The application I'm building will be using WWF as the core, and I'm facing a difficult decision regarding the backend support.

I want it to reach a wide group of people but at the same time I'm inclined not to support MS Access at all (and remove all code related to it), and focus only on MSSQL, because I think that those that still use MS Access will sooner or later upgrade to MSSQL, I need to know your opinions on this matter, as supporting both backends will require a great deal of time, you know adding design to one and then the other is too much.

Please vote and be fair.
Thx.

Gullanian wrote: The code change between the two isn't much anyway most likely.

Thats not always true, I often use quite complex stored procedures in SQL Server and some of those could not be easily rewritting in access. Well at least without making multiple queries

That's the kind of thing I'm trying to avoind, having to develope scalable code to support both backends, that will take twice as long, not to mention having to debug and test both, I know some people still use Access, but the trend will be to move away from it sooner or later. On the other end, I could be doing a critical mistake by not supporting Access, since I want a wide audience, that's the purpose of starting this poll.

Also, it depends who the application is aimed at. If it is high end (i.e. aimed at corporate customers and needs to be very scalable) or aimed at the lower end that want a quick and easy to use datasource but are not too worried about scalability.