Volian/SourceCode
8
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed issue of Import Procedure has same RO Path but a different ROdbid number

Browse Source 
Fixed issue where the top box of the dialog was not displaying the “&” character used in the RO Path
This commit is contained in:
John Jenko
2016-07-26 15:25:48 +00:00
parent 146e1fb968
commit 254d15948f
2 changed files with 21 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
PROMS/VEPROMS User Interface/dlgExportImport.cs
View File

@@ -220,6 +220,15 @@ namespace VEPROMS
MyRODb = RODb.GetJustRoDb(rodbid);
oldRODbID = newRODbID = rodbid;
break;
}
// B2016-175 have the correct (matching) RO Path but the rodbid is different (procedure came from a different SQL database)
// We can use the RO Path but we need to change the rodbid in the RO links of the procedure we are importing
else if (dbi.FolderPath == rofolderpath && dbi.RODbID != rodbid)
{
MyRODb = RODb.GetByFolderPath(rofolderpath);
newRODbID = MyRODb.RODbID;
oldRODbID = rodbid;
break;
}
else
{