In short it should be as safe as it was before no need to recompile
If there were schema changes then if you tried to run the fix it would fail with a CRC error in most cases. Server side progress code only needs to be recompiled when the schema has changed or any include / libraries may have changed. Or different platform, SQL / Progress / 32Bit / 64Bit.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of tkoch77
Sent: 14 May 2012 16:04
To: vantage@yahoogroups.com
Subject: [Vantage] Running Progress Program
Epicor provided us a Progress Program patch which was designed for Database version 9.05.606A Progress 64bit. We have since upgraded to 9.05.607B and need to run this patch again. I talked to tech support and the guy told me I can run this patch safely on our 607B database because there wasn't a schema change. Should I be having them build me a patch for 607B or is it safe to run this "old" patch?
Thanks,
Ted
[Non-text portions of this message have been removed]
If there were schema changes then if you tried to run the fix it would fail with a CRC error in most cases. Server side progress code only needs to be recompiled when the schema has changed or any include / libraries may have changed. Or different platform, SQL / Progress / 32Bit / 64Bit.
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of tkoch77
Sent: 14 May 2012 16:04
To: vantage@yahoogroups.com
Subject: [Vantage] Running Progress Program
Epicor provided us a Progress Program patch which was designed for Database version 9.05.606A Progress 64bit. We have since upgraded to 9.05.607B and need to run this patch again. I talked to tech support and the guy told me I can run this patch safely on our 607B database because there wasn't a schema change. Should I be having them build me a patch for 607B or is it safe to run this "old" patch?
Thanks,
Ted
[Non-text portions of this message have been removed]