[jonmorris04]

Hello,

Is it safe to VO code or FDL code SAS3 when EsysPlus reports "Unable to fix data version"? I am using Esys 3.36.2 & Plus 4.0.2. I've tried with data versions 4.33.31 and 4.34.10. The CAFD is in the base data but I don't think Plus supports it just yet. Fix by reference seems to do a decent job.

Thanks.

[masa52]

strange
I have latest software and dont have this issue
your cafd looks old
latest is 003.005.008
inject again cafd and try it

[jonmorris04]

strange
I have latest software and dont have this issue
your cafd looks old
latest is 003.005.008
inject again cafd and try it

Any problems injecting and coding 003.005.008 when its on 003.005.006?

[xxiFear]

strange
I have latest software and dont have this issue
your cafd looks old
latest is 003.005.008
inject again cafd and try it

Any problems injecting and coding 003.005.008 when its on 003.005.006?

Esys takes care of compatibility. If you can inject it, it will work.
Be aware, that „fixing by reference“ has a high risk of you coding something you don’t want to because the „fix“ is off. Especially when taking Parameter names from different CAF subversions and mapping them by memory location…

[jonmorris04]

strange
I have latest software and dont have this issue
your cafd looks old
latest is 003.005.008
inject again cafd and try it

Any problems injecting and coding 003.005.008 when its on 003.005.006?

Esys takes care of compatibility. If you can inject it, it will work.
Be aware, that „fixing by reference“ has a high risk of you coding something you don’t want to because the „fix“ is off. Especially when taking Parameter names from different CAF subversions and mapping them by memory location…

Thank you for the info. I tried injecting the CAFD, but I'm still receiving the message. The CAFD is showing as updated in the module. I injected 003.005.007, but it's still showing the fix dialog.

[Node]

It clearly does not have ...03.05.xx mapping. Last mapping in the list is ...03.04.xx.

[xxiFear]

strange
I have latest software and dont have this issue
your cafd looks old
latest is 003.005.008
inject again cafd and try it

Any problems injecting and coding 003.005.008 when its on 003.005.006?

Esys takes care of compatibility. If you can inject it, it will work.
Be aware, that „fixing by reference“ has a high risk of you coding something you don’t want to because the „fix“ is off. Especially when taking Parameter names from different CAF subversions and mapping them by memory location…

Thank you for the info. I tried injecting the CAFD, but I'm still receiving the message. The CAFD is showing as updated in the module. I injected 003.005.007, but it's still showing the fix dialog.

Assuming from that dialog, they put all patch versions into one subversion with 000 at the end for their mapping. So that means they don’t have any 3.5.x mapped yet. You must be on 3.4 to edit it.

[jonmorris04]

It clearly does not have ...03.05.xx mapping. Last mapping in the list is ...03.04.xx.

Yes, so the mapping is missing from EsysPlus until they add newer base data mappings since this cafd is from 22.03 and they support up to 21.07. Correct?

[masa52]

I dont understand I have same esys plus 4.02 installed and Im able to fdl SAS3
updated yesterday to 03/22 ilevel and no problem
I Suggest reinstall program

[jonmorris04]

I dont understand I have same esys plus 4.02 installed and Im able to fdl SAS3
updated yesterday to 03/22 ilevel and no problem
I Suggest reinstall program

I tried this on the same laptop, and on a new laptop with a fresh Windows install with the same result.