>One thing that would concern me is ensuring backup of the sql server data at the client locations. If I understood you correctly, each client will have their own copy of SQL Server Express? Not a bad plan, as long as you can ensure it is installed and configured in a standard manner, stored on a reliable system, and good backups are put in place. Then what about security?
>
>You would want to ensure everyone has the same standard install and configuration done and the same backup plans for easy maintenance. who would do that? Just stuff to consider. You might look at this:
>
>http://www.brianmadden.com/content/article/How-to-Automate-the-Backup-of-a-SQL-Server-2005-Express-Data-Store
___

I'm just thinking aloud - the whole app has to be (re)written anyway and I'd like a reasonable start ( != bad start)


For the client locations ( non accountant ) - I'll have to figure out a means of backup to file or so on another drive (zip or whatever). Currently many have their data on a file server that is going through a backup procedure anyway

I'm looking for a means to avoid installing sql server express at those sites and using the native driver. Now, Viv has pointed that I would need installing sql server anyway. But since my name might have been Thomas, I'll verify that and test it

I want an install for the average client, not complicated (most of them don't know how to start the windows explorer - but luckily they call the accountant - haha). What I'm afraid of is sql services that do not start, ......

As to security, I'll use sql server authentication, with a standard password built into the app. Yes, I know, I shouldn't but I will anyway for obvious reasons