client(valleywide): init app modernization project — VB6/Access stack analysis
Initial research session for VWP application modernization. Analyzed 2.7GB application archive, mapped ~130-table Access 97 schema via binary scan, confirmed VB6 + P-Code compilation (decompilation viable), and identified compliance requirements (certified payroll, 3-bank positive pay). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
51
clients/valleywide/app-modernization/CONTEXT.md
Normal file
51
clients/valleywide/app-modernization/CONTEXT.md
Normal file
@@ -0,0 +1,51 @@
|
||||
# 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
|
||||
Reference in New Issue
Block a user