I posted a message on the Forum on this topic last November, and while we did discuss it a bit, unfortunately nobody from Servoy piped up. I’ve also submitted this as a feature request, which now has a status of “open” and “unassigned”; not sure exactly what that means.
So, I thought I’d toss this out again in the hopes of getting a Servoy folk to inject a thought or two. Basically, I would like to be able to have 2 database connections in the Runtime version of Servoy in order to convert users of our old system to the new system. 2 database connections aren’t currently allowed in the runtime version of Servoy. There are a couple of other ways to accomplish this, but they require the user to have jump through various hoops to get it done. If nothing else, I’d like to understand why the runtime version is limited to one connection.
I am blithely hoping that the reason might be something like, “OH, that’s just because of this flag that is set to “off”. We can just set that to “on” and you’ll be ready to go”. I know, an incredible amount of wishful thinking. But, hope springs eternal.
As always, thanks for any guidance you can provide.
Sometimes the Runtime version of Servoy (which is a standalone version of Servoy disconnected from any application server) is confused with the Servoy smart client as opposed to Servoy Developer. Indeed the Servoy runtime environment supports only one database connection, but the far more often use smart client that works together with the application server does not have this restriction.
I understand that you have 2 databases connected to servoy and you want to switch from one to another? You can use databaseManager.switchServer() for this proposal. If not is this that you want tell me more.
Thanks for taking the time to respond. Appreciate it.
My question was specifically about the runtime version of Servoy, which currently only allows one database connection. I’ll take a look at “switchServer”, but I don’t think that that’s an option for me. I have current customers which are using a runtime version of Microsoft Access as the underpinning to the application. To move them to the new version, I need to be able to open their access database, and extract the data, moving it to the new Postgres database in the Servoy runtime. It turns out that this is even an issue in the saas versions of Servoy, just a bit easier to deal with. The solution right now seems to be to have a separate Access app that will open the database and dump all of the data in Excel spreadsheets, or something similar, and then open these files in Servoy to load the new Postgres database. That’s do-able, just a pain in the neck.