sync: auto-sync from Mikes-MacBook-Air.local at 2026-06-14 08:36:19
Author: Mike Swanson Machine: Mikes-MacBook-Air.local Timestamp: 2026-06-14 08:36:19
This commit is contained in:
@@ -5,11 +5,13 @@ display_name: Valley Wide "Orders" App Modernization
|
||||
client: valleywide
|
||||
status: active
|
||||
last_compiled: 2026-06-14
|
||||
compiled_by: GURU-5070/claude-main
|
||||
compiled_by: Mikes-MacBook-Air/claude-main
|
||||
sources:
|
||||
- clients/valleywide/app-modernization/CONTEXT.md
|
||||
- clients/valleywide/app-modernization/source-code/Orders-VWP_Current-2020/
|
||||
- clients/valleywide/app-modernization/docs/MODERNIZATION_ROADMAP.md
|
||||
- clients/valleywide/session-logs/2026-06/2026-06-13-mike-vwp-server3-migration-and-orders-source-recovery.md
|
||||
- clients/valleywide/session-logs/2026-06/2026-06-14-mike-orders-modernization-roadmap.md
|
||||
- wiki/clients/valleywide.md
|
||||
backlinks:
|
||||
- clients/valleywide
|
||||
@@ -135,6 +137,47 @@ The three commercial controls map cleanly onto modern equivalents from the **sam
|
||||
|
||||
---
|
||||
|
||||
## Modernization Roadmap (2026-06-14)
|
||||
|
||||
A comprehensive 7-phase roadmap has been established for migrating ORDERS from VB6/Jet to a modern web application. The strategy uses a **dual-client architecture** (strangler pattern) where both VB6 and web clients share the same SQL Server backend during development, enabling gradual module-by-module migration with real-user beta testing.
|
||||
|
||||
**Full roadmap:** `clients/valleywide/app-modernization/docs/MODERNIZATION_ROADMAP.md`
|
||||
|
||||
### Core Strategy
|
||||
|
||||
1. **Jet → SQL Server migration first (Month 1)** — Removes 2GB limit and Win7 VM dependency. VB6 `modADO.bas` updated for SQL Server connection strings.
|
||||
2. **Dual-client architecture (Months 2-9)** — VB6 and web client coexist, both accessing SQL Server. Enables live-beta platform with 3-5 real users testing web modules while production continues on VB6.
|
||||
3. **Module-by-module rollout** — Read-only modules first (project lists, reports), then light data entry, then complex modules, with certified payroll and positive pay last (compliance-critical).
|
||||
4. **Single cutover to SQL storage** — No migrate-twice. Once SQL Server is live, both clients use it. Web client gradually replaces VB6 modules until full cutover.
|
||||
|
||||
### Timeline (8-9 Months)
|
||||
|
||||
| Phase | Duration | Focus | Key Deliverables |
|
||||
|---|---|---|---|
|
||||
| 1: Foundation & Database | Month 1 | Jet→SQL migration, modADO update | SQL Server live, VB6 on SQL verified |
|
||||
| 2: Web Foundation & API | Month 2 | REST API, auth framework | API layer operational, auth working |
|
||||
| 3: Read-Only Modules | Months 2-3 | Project lists, reports, view-only forms | 3-5 beta users testing read access |
|
||||
| 4: Light Data Entry | Months 3-4 | Simple CRUD forms (inventory, contacts) | Beta users entering new data via web |
|
||||
| 5: Complex Modules | Months 5-6 | Takeoffs, change orders, job costing | Core business logic migrated |
|
||||
| 6: Compliance Modules | Months 7-8 | Certified payroll, positive pay (3 banks) | Legal requirements met in web client |
|
||||
| 7: Full Rollout | Months 8-9 | Remaining modules, training, cutover | All users on web client, VB6 retired |
|
||||
|
||||
### Technical Safeguards
|
||||
|
||||
- **Row versioning** — SQL Server optimistic concurrency prevents VB6/web conflicts
|
||||
- **Feature flags** — Per-module rollback capability if web version has issues
|
||||
- **Audit logging** — Track which client type (VB6/web) performed each operation
|
||||
- **Blazor Server/.NET 8 recommended** — Strong data binding for complex forms, .NET ecosystem alignment
|
||||
|
||||
### Risk Mitigation
|
||||
|
||||
- **Crystal Reports** — 791 reports preserved initially via Crystal for .NET runtime; gradual re-platforming to modern reporting engine (SSRS/DevExpress) in Phase 7
|
||||
- **OCX grid logic** — Business rules in True DBGrid/FarPoint event handlers migrated to API layer validation + web UI bindings
|
||||
- **Beta user feedback loop** — Each module tested by 3-5 users before general rollout
|
||||
- **Parallel operation** — VB6 remains production-ready throughout; web rollout is additive, not replacement, until Phase 7
|
||||
|
||||
---
|
||||
|
||||
## Source Code Status & Locations
|
||||
|
||||
- **Recovered tree (repo):** `clients/valleywide/app-modernization/source-code/Orders-VWP_Current-2020/`
|
||||
@@ -157,6 +200,7 @@ The three commercial controls map cleanly onto modern equivalents from the **sam
|
||||
| 2026-05-14 | Ticket #32280 "Source Code Data Recovery" opened. |
|
||||
| 2026-05-16 | VB6 source search across server drives (D/drive2/drive3 scans) — substantial VB6 found, confirming which is VWP's was in progress. |
|
||||
| 2026-06-13 | **Full source recovered** from `Darv.rar` (WINFileSvr). Staged to repo; decompilation retired. Found during the SERVER3→VWP-FILES G: migration server sweep. |
|
||||
| 2026-06-14 | **Modernization roadmap established.** 7-phase dual-client strategy (8-9 months): Jet→SQL migration first, then gradual web development with strangler pattern. Syncro ticket updated with source recovery announcement. |
|
||||
|
||||
---
|
||||
|
||||
|
||||
Reference in New Issue
Block a user