Usually a fix release (with a .digit on the end) is not a complete release, and just replaces a few bits of the parent release. You will need to install 11.6.SP3 first, and I don't think the full Service packs are available for download, so you will need to contact AVEVA and get a CD sent to you.
Thanks Tim...you were right....i had to request a CD fro Aveva which i got it today.....and after sp3 installation i was able to ru sp3.6...
just wanna make sure one thing..when i ran the sp3 installation, it didnot automatically detect my old sp2.2. installation...therfore i simply selected the same folder where my sp2.2 version was installed when prompted for the installation folder....and installtion was completed without any erors......and checked with help about, and its now showing sp3.6you reckon is dat ok ?
I don't know I am afraid. I usually install them in parallel (different folders), but that is because I want to test interfaces against several different service packs. sp2 and sp3 probably have very similar lists of files, so I would expect that it would not cause problems
how do you guyz incooperate the in-house customizations when a new patch comes.....At the moment am having the following problem
We have added a few customized menus in the piping module...for that we copied the aveva object file to our company's PML folder and did the modifications.....now if the new patach or release changes anything in the piping menus and stuff....do we have to copy our customizations to the updated object file ?.....or wat should be the best way to do customizations...like adding menus and stuff....
Somebody on this forum suggested not to touch the std aveva files, therefore we copy the std files to the company PML folder location (which is first in PML path) and then add our code ..please advise a better way if one exist as the above method will lead to problems or rework when a new patch of release comes.....
Example..with sp3, aveva reintroduced the Query => General... option...but when i installed sp3, the Query => General... option didnot show up..and I belive this is because we have two object files with same name and the program will always use the forst one (which is out sustomized one in the compamy PML folder.....any ideas ??
Well, I solved in such way that I first have a version specific customisation folder, then the normal customisation folder and last the AVEVA standard folder.
This because menu files, standard forms and objects normally change, but the rest of the customisation work can be kept the same between software versions(especially those completely made by yourself).
I agree, i have a different pmllib and pdmsui folder for each new version. I have not done it for ww.6.sp3, I just rolled out sp3 and haven't had any problems using the 11.6.sp2 directory. In fact, I'm just going to use 116 as the dir name for the entire release, until I hit a bump, then I'll start breaking it up.
