Cpt critcal path hot fix

[ryanbeard82]

Purpose

Resolve issues with Driving Paths vs Driving Path button.

Remove resource names from the default driving path view.

Pre-Merge TODOs

• Execute module updates, including version number increments for both .bas and .frm files
• Update the "CurrentVersions.xml" to reflect latest versions of updated modules

Pull Request Submittal Checklist

• Assign Code Reviewers
• Tag with appropriate designation (e.g. Bug, Issue #, etc)

Pull Request Approval Checklist

• Review Code Changes
• Verify updates to "CurrentVersions.xml" and .bas/.frm version numbers

[AronGahagan]

please update to v3.4.2 (and the *_frm module also if not already)

[ryanbeard82]

Help me out. The .bas was already updated. Are you saying you want the form revisioned arbitrarily  as well just to keep up?

…

-ryan

On Jan 30, 2026 at 7:17 PM -0600, Aron Gahagan ***@***.***>, wrote: @AronGahagan requested changes on this pull request. In CurrentVersions.xml: > please update to v3.4.2 (and the *_frm module also if not already) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>

[AronGahagan]

Help me out. The .bas was already updated. Are you saying you want the form revisioned arbitrarily  as well just to keep up?
…
-ryan
On Jan 30, 2026 at 7:17 PM -0600, Aron Gahagan @.*>, wrote: @AronGahagan requested changes on this pull request. In CurrentVersions.xml: > please update to v3.4.2 (and the _frm module also if not already) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.>

I assumed the "feature" has a version, and since the feature an associated .bas and .frm they would reflect the 'latest version' of the "feature" -- that's how the other cpt features are handled -- BUT if you don't want to do it that way, totally fine, your call, these are your modules. I can mark it resolved an pull it. Let me know.

[ryanbeard82]

Help me out. The .bas was already updated. Are you saying you want the form revisioned arbitrarily  as well just to keep up?
…
-ryan
On Jan 30, 2026 at 7:17 PM -0600, Aron Gahagan @.>, wrote: @AronGahagan requested changes on this pull request. In CurrentVersions.xml: > please update to v3.4.2 (and the __frm module also if not already) — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: _@.*>

I assumed the "feature" has a version, and since the feature an associated .bas and .frm they would reflect the 'latest version' of the "feature" -- that's how the other cpt features are handled -- BUT if you don't want to do it that way, totally fine, your call, these are your modules. I can mark it resolved an pull it. Let me know.

Done. Tested beta update - confirmed form and bas operate as expected.