revOpenDatabase()

[Marek Niesiobedzki]

Hi Bill,

For me are 5 valid reasons:

1. Compatibility of code if using two or more kind of db's in one solution - you change only one connection command and the rest is common (under codition of using standard SQL queries). 

2. You can start using Valentina when you are learning it's specific API and test it. Having db builded and working it's easier to introduce it's expanded posibilities step by step.

3. I'm using DataGrids which are easy working with rev functions. I'm not sure if it's so easy with native Valentina methods without using 3-d party software (such as SQL Yoga - which you must buy and learn). Of course it's in my menu to check it, but as desert.

4. Until now I was using SQLite and MySql db's, so I'd like to just switch to one kind - Valentina. There can be only problem wit using it as embeded engine in mobile applications, so SQLite will still be used. But in reference to p. 1 it's easy to swap each other.

5. The most important as I think is to have possibility to check possibilities an compare Valentina with other db's in the same conditions first, and then make the same using Valentina native methods. You can compare the speed and stability under different conditions all of solutions so you can choose the best for you.

Maybe there are mor reasons to have more possibilities than less of them. I hope if it's working well there will be more customers wanting to check and start to use it.

Best regards,
Marek