|
Hi. We create software with PowerBuilder to run against SQLA. We seem to have found that when our developer's copy of SQLA is more than a few versions ahead of our customer's copy of SQLA, problems may develop. For instance, our developers now develop with PB12 against SQLA12. Customers who are running SQLA8 are (depending on the app functions they use) likely to have (what are often) subtle problems which are eliminated, if they upgrade SQLA. At the moment, it seems our customers who are running SQLA9 and above, are fine. Is there any way to know the minimum SQLA versions our customers need to be running? |
|
Basically you have two choices.
1
We do something like 2: we always support 3 versions of SA (currently 10,11,12). Our customers may use their older versions as long as they please, but that might not be compatible with the current version of our software.
(19 Jun '12, 07:13)
Reimer Pods
2
FWIW each deployed version of Foxhound requires a certain minimum version AND build of SQL Anywhere to run on. Target databases can run on anything from 5.5 and up, but not Foxhound itself... it won't even start. The whole idea of testing multiple combinations of older versions gives me the heebie jeebies, let alone trying to support untested combinations. So far (touch wood) allowing newer-than-minimum versions of SQL Anywhere hasn't resulted in any trouble reports.
(19 Jun '12, 09:08)
Breck Carter
Replies hidden
1
Yes, checking "@@select version" at program setup (and/or at program start) and stop with an according message if the installed SQ version doesn't meet the (minimum) requirements is our preferred behaviour, as well...
(19 Jun '12, 09:16)
Volker Barth
|
There is no gear to determine the minimum SQL Anywhere versions requirements for an application. We do document new features and behaviour difference to highlight changes that could impact an implementation. Testing is needed to verify that any specific version of SQL Anywhere is suited for a particular application.
For context, what specifically are the subtle problem(s) your customers are seeing. And what version and build are being used when the problems are seen?