(questions and doubts in bold)
I'm still trying if our applications could have a future on the web cloud without:
- completely having to re-writing everything in one go,
- or having to keep different versions of our databases (meaning different providers)
- have less competitive pricing (unless Postgresql would be used, if that DB IS fully supported now?).
- not being able to follow the "hybrid / gradual" migration to n-tier on a web server, as described by Appeon in Elevate
but I'm stuck with the same thing: It seems that Appeon does not allow "Other" ODBC / OLEDB drivers for our database of choice for the .Net cloud migration (Tibero). I don't really know why you even can configure a database connection on Appeon WEB (.Net) as "Other" when it's not supported?
We could look into the Appeon J2EE server installation, but then all of our connections would have to be JDBC and I suppose that in that case we would not be able to use our .Net services and possible workarounds? (I'm a noob so not sure).
Am I correct in giving up, or is there a way? (like Appeon supporting "Other" databases or combining another server for .Net ?)