>If you have up to 15 users per customer, that points more towards a C/S backend for security and integrity reasons. However, 15 is more than you are allowed with the "free" versions of commercial databases. To use SQL Server, for example, you'll need licenses.
>
>This brings 2 decisions:
>
>1) Are your customers willing to pay $ for a database license to upgrade to your new version, especially if competitors are retaining local or other free storage.
>
>2) Who will maintain the server. Make no mistake, maintaining a database server does take time and expertise.
>
>The next option is an open source C/S database. There are several of these becoming common in small business. If you decide to use one of these, there are people willing to provide advice in this forum. HOWEVER, check out the license very carefully- there may still be a charge if you distribute the database commercially. There is also the issue of support - "somebody" will have to look after the server at your customers.
>

We will have to provide both local ( current customers ) & C/S databases ( for new Customers who currently do not look at our s/w at all, but, in a phased manner )

>Then there is the option of staying with local tables. from memory, many PCs in india have their own UPS which hopefully helps prevent many corruptions. Again, you know your customers better than we do... how much corruption do you see, and will your customers be willing to pay the price for C/S to avoid it?
>

Yes. All my Customers have UPS & data corruption is less.

>As for security - what is your customers' expectation?
>

We don't have that type of Customer for whom security is a issue. Since my s/w is DOS based, they don't even call us.

I thought type/technology of data storage was unimportant. We have to choose between VFP/.Net/or any other devp. platform.

The Application that we are developing will take atleast 3 years to mature & be competive. Then it will enter maintenance mode/minor changes ( no focus on technology )

Can you help us decide ?

Rakesh