>>>A short while ago I wrote about our wish to migrate a successful vfp app to a language with a more abundant developer supply long term.
>>>
>>>As a cautious first step, we think it would be good to start with a smaller new and related app in order to gain experience. So this thread is about that new app. A big goal is to choose tools that give developer productivity and avoid the need to write repetitive code.
>>>
>>>So far we are leaning in the following ways but are open to suggestions:
>>>1) Web based
>>>2) .NET
>
>I'd use Xamarin if you want something .NET based to have an option to run on Linux backend (see #1) and easier way into mobile for the future.
>
>>>3) Undecided between SQL Server and MySql for reasons of cost to customer vs advantages to developer (what are the advantages to developer?)
>
>seconding Craig for Postgres. Use MariaDB if you really need MySQL compatibilty (similar to Open Office vs. Libre Office, and I dislike Oracle, even if I have to use Java)
>
>
>>>4) Use tools that automate database evolution at user site
>>>5) Use tools that simplify business rule evolution with valid date range for the rules
>
>Go for something backend DB server based but vendor agnostic like toad
>
>>>6) We would *really* like it if the tools we chose allow us to store some BusinessObject attributes in Object-Attribute-Value form rather than exclusively as columns in a table
>
>Instead of going MongoDB or a special "bag" table with Qualifier(s)-Attribute-Value structure perhaps a special field holding an XML or (my favorite) JSON object
> can be added to some tables or one table with added qualifiers(s), adding limited document ability to relational DB. Stay away from overusing special vendor API implementing this (Postgres or MS SQL) and access such data at a low, but common level to stay DB vendor independant.

Thank you Thomas. Alex