#Compatibility

7

Compatibility is the capacity for two systems to work together without having to be altered to do so.

I have one in my testing environment. According to https://community.intersystems.com/post/licensing-ubuntu-and-suse-20171-and-later, I should move to native Ubuntu build with 2017.2. So I downloaded Cache for UNIX (Ubuntu Server LTS for x86-64) 2017.2.1 and tried to update my existing 2015.1.4 installation. What I got was:

Upgrade from lnxsusex64 platform is not allowed.

0 4
0 421

I'm having trouble with a vb6 application attempting to connect to a Cache 2017 release. It uses the older Cacheobject.dll instead of ActiveX. The application currently works with a 2010 release of Cache. Is Cacheobject.dll supported in later releases?

I looked through documentation and posts and did not find an answer.

Thanks in advance for any response.

0 1
0 515

I was wondering if there was a way to if the user is using Studio and changes a file to get the users name and have a function run when the file is changed.

Ive got this working for .int files but not for .csp or .js or .css or any other kinds of files.

When we edit code we are logged in to the Cache backend’s server through Studio by using an iPaddress (which is on our network).

I know now there are concepts of file locks and logs for when certain tasks are ran or when a user maybe edits a file

0 5
0 442

When I open a BPL in Atelier and right click 'Open diagram editor' I get a Java Incompatible browser error message (see below).

I'm using Windows 8.1, Atelier 1.0.190 and IE 11.

All the M.S. updates are up to date.

I also have firefox and chrome installed.

Trying to change default browsers etc. did not work.

0 5
0 474
Announcement
· Aug 25, 2016
JSON changes in Caché 2016.2

As Bill has mentioned earlier in his post, we have carefully reviewed the JSON capabilities and made some adjustments to ensure they deliver the best benefit to you. In this post, I am going to describe the modifications in more detail and provide guidance for you to understand the implication for your code base.

11 8
1 4K
InterSystems Official
· Apr 27, 2017
VSI OpenVMS

The last version of Caché, Ensemble released for VSI OpenVMS is 2017.1. Unlike HP OpenVMS (Alpha and Itanium), VSI OpenVMS on Itanium continues to be supported. This means that critical corrections or changes required to support customer’s hardware purchases will all be based on 2017.1 or earlier versions.

Related announcement: https://community.intersystems.com/post/platform-compatibility-hp-open-vms

0 0
0 967
InterSystems Official
· Dec 7, 2016
Platform Compatibility: HP Open VMS
Post has been edited for clarification: Both HP Open VMS versions (for Itanium and for Alpha) are discontinued for future InterSystems releases.
Future product releases, beginning with the next major release after 2017.1, will no longer be offered for the following platforms:
HP OpenVMS for Itanium
HP OpenVMS for Alpha
Products: Caché, Ensemble
Expected Availability: next major release after 2017.1
3 1
0 1.2K

The class %Compiler.UDL.TextServices arrived in 2015.1, bringing us methods for exporting a class in UDL format (i.e. looking just like we're used to seeing it in Studio), and importing a UDL format definition back into a namespace. Some source control tools including our Deltanji are now able to use UDL format, resulting in diffs that are easier to understand.

1 1
0 373

This announcement is to inform clients about changes in our 2016.2 and 2016.3 field test programs.

The 2016.2 field test has been extended in order to address important syntax changes related to JSON. Simply stated, the JSON syntax introduced in 2016.1 had several inconsistencies that we did not want to perpetuate. This is now addressed and the updated 2016.2 field test will be published today. Concurrently, the syntax changes and guidance for developers will be posted on the Developer Community shortly. JSON is critically important to our Caché roadmap.

8 11
0 1.5K

We are finally planning to migrate some ancient Caché applications that are run on Caché 5.0.21 to a new server with Caché 2016.2.0 or so.

I wonder if we could use Shadowing between those to keep the data on the new server up to date?

We would copy the Caché backup from the old environment to the new and do a RESTORE there and then start shadowing.

I know than 5.0.21 is no more officially supported by ISC.

0 5
0 780