December 24, 2009 at 10:40 am
why not just go from vb straight to mysql.
it's a lot easier and faster than going from mssql to mysql.
December 28, 2009 at 4:36 am
Thanks for your reply Alex!!
I thought too. But in our organization we have two diff. networks, one for production and another for non-production.
Mysql is being used for an enterprise application and is kept in the non-production network, but end user desktops will be connected only to production network as per our compliance guidelines :blink:. So, our only option is go through mssql 2000 which is lying the production network which has the limited access to few servers in the non-production servers.
Thanks in advance.
December 28, 2009 at 11:54 am
Viewing 3 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply