Files
claudetools/clients/valleywide/app-modernization/CONTEXT.md
Mike Swanson fccf9f9468 sync: auto-sync from GURU-5070 at 2026-06-14 05:33:01
Author: Mike Swanson
Machine: GURU-5070
Timestamp: 2026-06-14 05:33:01
2026-06-14 05:34:46 -07:00

95 lines
4.8 KiB
Markdown

# Valleywide App Modernization — Project Context
## Client
Valley Wide Plastering (VWP) — `valleywideplastering.com`
## Overview
VWP uses a custom business application of unknown exact stack (suspected MS Access and/or Visual FoxPro). The original developer is deceased. The app still runs but is hitting end-of-life limitations. Goal is to assess feasibility of modernization — either as a web app or a modern desktop executable.
## Known Constraints / Pain Points
- **2GB database file limit** — strongly suggests MS Access (.mdb / Jet engine). VFP uses per-table .dbf files so a single 2GB wall is more characteristic of Access.
- Original author deceased — no support, no documentation expected
- Unknown whether VFP is actually involved — confirm once source materials are received
## Stack Hypothesis (pre-source)
| Layer | Likely | Notes |
|---|---|---|
| Database | MS Access .mdb (Jet 3.x/4.x) | 2GB single-file limit is the tell |
| Frontend | MS Access forms OR Visual FoxPro | Need source files to confirm |
| Language | VBA (if Access) / FoxPro (if VFP) | |
Visual FoxPro EOL was 2015. MS Access Jet/.mdb is still technically supported but ancient.
## Source Materials Needed
- The .mdb or .accdb file (database + forms if pure Access)
- If VFP: .prg, .scx, .vcx, .frx, .dbf, .fpt, .cdx files
- Any .exe or compiled application if available
- Screenshots or walkthrough of what the app does
## Research Questions (Phase 1)
1. What is the exact stack? (confirm Access vs VFP vs hybrid)
2. How many tables? Approximate row counts?
3. What business processes does it cover? (estimating, job tracking, billing, scheduling?)
4. How many concurrent users? On-prem only or remote access needed?
5. Does it integrate with anything? (QuickBooks, email, external data sources?)
6. What are the specific pain points beyond the file size limit?
## Target Options
| Option | Pros | Cons |
|---|---|---|
| Web app (browser-based) | No client install, remote access, no file limits | More dev work, requires hosting |
| Modern desktop executable | Closest to current UX, works offline | Still requires client deployment |
## Status
- [ ] Receive source materials from VWP
- [ ] Identify exact stack
- [ ] Catalog tables and data volume
- [ ] Map business processes
- [ ] Produce feasibility report with stack recommendation
## Session Logs
- `session-logs/` — work logs for this sub-project
---
## Update 2026-06-13 — Darv source recovery from migrated G: drive
During the G: file-share migration (SERVER3 -> VWP-FILES, Hyper-V), Darv's full user
profile was found on the G: volume at `G:\Users\Darv` (now `\VWP-FILES\G-drive\Users\Darv`).
**Source code status — still effectively lost:** `G:\Users\Darv\Source\VWP` contains ONLY
`frmPayroll.frm` (+ `.frx`, 32 KB, 2017) — the same single form found earlier on ADSRVR.
No `.vbp` project file, no other forms/modules. The 19 `.vbp` / 44 `.frm` elsewhere under
`Darv` are Crystal Reports 8.5 SDK samples (`Darv\Installs\SCR85Dev`), not the app.
**New compiled/data artifacts recovered** (staged to `source-analysis/darv-G-finds/`):
- `ORDERS0727-2015.exe` (7.3 MB, built 2015-07-27) — from `Darv\OrdersPkg\Package1508\Support\`.
Newer compiled build than `Orders_10A.exe`; primary VB Decompiler target.
- `ORDERS-2005.exe` (5.2 MB, 2005) — older build.
- `Package1508/` (60 MB, 88 files) — the InstallShield/PDW deployment package for the 2015 build.
- `frmPayroll.frm` / `.frx` — the one surviving source form.
**On G: but NOT pulled (large):** `G:\Users\Darv\VWP\db1.mdb` (120 MB, 2017) — likely VWP
data DB; plus other Darv-project DBs (HealthCare/ACA). Pull on demand.
**Next:** run VB Decompiler Pro against `ORDERS0727-2015.exe` (P-Code -> ~70-80% recovery).
---
## Update 2026-06-13 (later) — SOURCE FULLY RECOVERED (supersedes "still lost" above)
The complete VWP "Orders" VB6 source was recovered from **`F:\Darv\Darv.rar`** on
**WINFileSvr (192.168.0.35)** — a 51 GB backup of Darv's dev machine (extracted to
`F:\Darv\Darv-rar`, 135 GB). The full project tree is present, with multiple versions:
- **Newest:** `…\Kingston\Project\VWP_Current\ORDERS_C.vbp` (2020-06-09) — 128 `.frm`, 4 `.bas`;
`ORDERS_C` references 80 forms + 10 OCX (TABCTL32, Crystal `Crystl32`, True DBGrid, FarPoint Spread).
- Also: `VWP_Inv`, `VWP_Update`, `VWP_Current_0317`; historical `ORDERSold.vbp` (2002), `ORDERSSave`.
**Staged to repo:** `source-code/Orders-VWP_Current-2020/` — 12.2 MB pure source
(147 `.frm`, 4 `.bas`, 5 `.vbp`). Databases left on the server.
**Decompilation (VB Decompiler Pro) is NO LONGER NEEDED** — we have the real, buildable source.
Stack now confirmed from source: **VB6 (P-Code), Jet/Access `.mdb`, Crystal Reports, heavy OCX
dependency** (TABCTL32, True DBGrid Pro, FarPoint Spread, Flp32a30). Next: set up a VB6 build env
to confirm it compiles, then scope the modernization from actual source. Tracked on ticket #32280.