Hi Russell,



VistaDB looks very interesting but one thing I did not like it is that is a file share database, which means that each application instance needs to open the file database in order to access it, pretty much like VFP and I am not sure I want to go back to that kind of database.



On the other hand I did like all other features, specially their compatibility with MS-SQL which mean that it would probably be easier to implement in SF and our applications to switch from VistaDB to MS-SQL with less code change impact.



What I like about MySQL is that it is a real SQL database,portable and lightweight, reliable, and it can also be embedded and it is available in almost every hosting ISP at a very affordable price for everybody.



I have an application using MS-SQL Express and found out that one of the process needed will be importing thousands of records (sometimes 400,000+) and that those records should be keep in the database for comparison with new imports, that hits me very hard, because now the database file is growing up pretty fast and the only option would be to buy the MS-SQL Standard license and it was just unexpected and that would be the case for almost any customer using this application and that could hurt any possible sale. MySQL is very well suited to handle this application requirements but since it is not supported by SF/DDT/BOM/RBS then it would be very hard for me to manage and I use all SF tools in all applications.

Edhy Rijo

I agree with what you said about both VistaDB and MySQL. 

I am primarily worried about all the auditors who use my product on their laptops.  They never share anything and there is no need for them to do anything on a server.  They are strictly remote users who always upload their data (via SMTP now).  I take their data and upload it into SQL Server.  Right now because the numbers are relatively low with mostly longtime experienced users I can just barely handle everything but that will change as the year goes by. 

I also have a fair number of churches (21 now but growing rapidly this year (I hope anyway) using another of my VFP products.  I definitely don't want to use SQL Server Express for them either.  I am really going to be pushing the church product this year now that I am self-employed and can do whatever I want just time permitting.  All the churches using it now install it on a single PC, typically the pastor's or church secretary, and they don't care about multi-user capability.  It already supports it though in VFP I just have not yet run into any church doing it that way but I know it will happen.  My goal is to have over 100 churches by year-end.

I didn't even know you could use MySQL as an embedded DB like you can with VistaDB.  I will have to check into it.  Definitely that sounds even better than VistaDB then all things considered. 

Thanks

For the server side of things for corporate clients I currently use SQL Server but would definitely like to look into using MySQL.  Even more so if I have the clients using MySQL.

Russ Brown (Using C#2010/SQL Server 2008)

Thought I would go ahead and jump in here. Edhy (and Greg) it is funny that you bring up MySQL as this database is already on slate to make it into the framework. It doesn't come up often, but it is a common database that should be native in the framework. I cannot give you any exact dates on this, but it should not be too difficult to implement and is something that we plan on doing.



Greg, I also liked your idea about add-in tools in the BO Mapper. We are going to do a major overhaul of the BO Mapper and when we do we will take this into consideration. Thanks guys!

Trent, that is a great news I am ready for a very early beta, don't need all the features supported or the DDT just yet, but at least the BOM and SF connectivity to start up.

The project I have that will fit perfectly for MySQL is about 35% done, so if you are willing to start an early beta, please consider me to start testing.

Edhy Rijo

As soon as we have something you will be the first to know.

If possible I would still like to have support for VistaDB.

I checked into licensing for the MySQL Embedded Database Engine and it is cost prohibitive (for me anyway).  They require an upfront deposit about 40 times the upfront cost of VistaDB.  VistaDB is also a one-time cost that doesn't depend on the number of users.

Thanks for your consideration.

Russ Brown (Using C#2010/SQL Server 2008)

Thanks, Russell. We will take this into consideration.