Technical Products Group · ~2002–2017 · The digital successor to EZ-SNAP
The order-entry application that upgraded EZ-SNAP from film to digital.
SNAP was the direct successor to EZ-SNAP, rewritten end-to-end for the digital-camera era. Where EZ-SNAP captured photo orders on a Symbol PDT handheld next to a film camera, SNAP plugged the camera directly into the workstation — pictures pulled themselves off the camera via Microsoft WIA, EXIF tags carried subject + order metadata permanently bound to each image, and every shot got backed up to two locations simultaneously. The same nation's-largest school picture companies that bought EZ-SNAP through the late-1990s ran SNAP through the 2000s and into the mid-2010s — the platform stayed in production-floor service through approximately 2017.
Every picture, tagged at the camera and backed up before you finished the next shot.
SNAP rebuilt EZ-SNAP's studio-floor order-capture workflow on top of the digital-camera and Windows-XP stack of the early 2000s. The photographer set up the subject, the operator scanned the subject's barcode and picked the order package, the photographer pressed the shutter — and SNAP did everything else. Image pulled off the camera over Microsoft WIA, renamed with the job number / sequence number / subject ID / Kodak DP-2 format, EXIF tags written with the subject and order info, second copy written to the flash card in the camera dock as backup-and-digital-film, line of text appended to the job's import file for the lab's legacy system. The photographer never had to think about the file system; the lab never had to ask which image belonged to which order.
Microsoft WIA bridge — every popular cameraSNAP drove every digital SLR that shipped with a Microsoft Windows Image Acquisition (WIA) driver — Canon, Nikon, Kodak, Fuji, Sony — through the same operator UI. The custom `WiaCalls.bas` module bridged Visual Basic 6 to the WIA API so the workflow stayed identical regardless of which camera the studio standardized on.
EXIF tags bound to every imageAs each picture was taken, SNAP wrote the sequence number, the subject ID, and the order info directly into the image's EXIF tags using standard EXIF fields — permanently binding the metadata to the image at the moment of capture. Out-of-order images and out-of-sequence orders were no longer possible to mix up; the data traveled with the file wherever it went.
Dual-backup, "digital film"Every picture was backed up to two locations simultaneously — the workstation's internal drive AND a flash memory card mounted in the camera dock. The flash card doubled as portable "digital film" the photographer could hand off, and as the disaster-recovery copy if the laptop got dropped in the parking lot.
Four input modes, one operator UISubject ID, Product or Package #, and Quantity entry via keyboard, barcode scanner, touch-screen, or mouse — the same operator workflow worked regardless of how the studio chose to identify the subject. Carried over the Symbol-PDT-era discipline from EZ-SNAP into the Windows-XP-on-a-laptop era.
Disk space, managed for youAutomatic disk-space maintenance retained the maximum number of recent jobs within a configurable storage budget — no manual purges, no "my laptop is full at the worst possible moment" failure modes. On a standard early-2000s laptop, SNAP could hold more than 20,000 high-resolution images at once.
EXIF for new labs, text files for old onesEXIF tags handled the modern workflow; a per-job text file linking job # / subject # / order info to the image filenames handled labs whose ingest pipelines pre-dated EXIF awareness. SNAP wrote both at the same time, so the studio could switch lab partners without changing how the photographer worked.
A direct evolution of EZ-SNAP, rebuilt for the digital-camera era.
When the school-photography industry transitioned from film to digital in the early 2000s, Redmer Software's EZ-SNAP customer base had a clear successor product: SNAP. Same studio-floor workflow, same school-picture-company customer base, same operator UI conventions — rebuilt end-to-end on the digital-camera bridge (Microsoft WIA), EXIF metadata, and the dual-backup discipline that the digital era made both possible and necessary. The platform stayed in production-floor service through approximately 2017.
The nation's largest school picture companies
Olan Mills and the other major U.S. and Canadian school-photography customers that bought EZ-SNAP carried forward to SNAP as the studio floor went digital. Same buyer, same studio operator, same lab workflow — new camera technology underneath.
Every popular digital SLR, one operator UI
Canon, Nikon, Kodak, Fuji, and Sony — every digital-SLR brand of the early-to-mid-2000s shipped with a Microsoft WIA driver, and SNAP drove all of them through the same operator screen. Studios could standardize on whichever camera their portfolio team preferred; the workflow stayed identical.
Subject + order info baked into every EXIF header
The data travelled with the file. When a finished portrait came back from the lab months later for a reprint or warranty inquiry, the sequence number, subject ID, and order info were still in the image — no separate database lookup required, no possibility of mismatch.
Two backups, automatic
Every shot landed on the workstation drive AND a flash card in the camera dock simultaneously. Losing one didn't lose the picture. The flash card doubled as portable "digital film" the photographer could hand off; the internal drive ran the auto-disk-management to retain >20,000 high-res images at once.
Visual Basic 6 + Microsoft WIA
Built on Microsoft Visual Basic 6 (the workhorse Windows-XP-era desktop stack — `.frm` forms, `.ctl` user controls, `.bas` modules). The custom `WiaCalls.bas` module bridged VB6 to the Windows Image Acquisition API, surfaced through a `DriveControl.ctl` + `ExplorerControl.ctl` file-system UI for managing the job-by-job image inventory.
Per-machine licensing via AppSerializer
Bundled `AppSerializer.exe` issued per-machine license keys; the application's `modGetLicense.bas` validated them at startup. A late-1990s-style desktop-licensing posture that respected the customer's need to deploy SNAP across a sprawling studio network without phoning home — the same posture A1SI's CRM ships under today with its self-hosted social-media-management stack.
A studio-floor product that scaled
Fifteen years on the line, a generation of digital portrait studios.
SNAP shipped from approximately 2002 through 2017 — carrying the EZ-SNAP customer base across the digital transition and into the mid-2010s. The User Guide on file (SNAP '06, version 7.0) documents a mature product seven major revisions in; the source repo's `Snap10` directory carries the 2010-era build; the platform stayed in production-floor service through approximately 2017. Same Microsoft + custom-VB6-control engineering posture that runs through the rest of the Redmer Software / TPG photo-imaging line.
Era
~2002–2017
Company
Technical Products Group (TPG)
Cameras
Canon · Nikon · Kodak · Fuji · Sony (via WIA)
Stack
Microsoft VB6 + WIA · Windows XP
Why this case study matters
The successor-product case study from the Redmer Software / TPG photo-imaging line.
The successor product, done right
When a customer base needs a successor product, the engineering call is whether to rebuild from scratch or carry the operator workflow forward. SNAP carried EZ-SNAP's operator workflow forward — same Subject ID / Product / Quantity capture, same barcode-scanner-and-keyboard input model, same studio-floor UI conventions — and rebuilt everything underneath for the new technology stack (digital cameras, Microsoft WIA, EXIF metadata, dual-backup). That successor-discipline shows up in A1SI's current product line whenever an older product retires (e.g., the CRM's social-media-management successor to legacy Hootsuite-style workflows).
Studio-floor reliability, automatic backup
Digital cameras introduced a new failure mode the film era didn't have: lose the flash card, lose the day's pictures. SNAP's dual-backup discipline — workstation drive AND flash card, automatic on every shutter press — turned that failure mode into a non-event. Same belt-and-suspenders posture that A1SI's CVWS commercial-vehicle weighing system ships under today (every weight record written to two places before the operator sees it).
Metadata baked into the file, not the database
SNAP wrote subject ID + order info into the image's EXIF tags at the moment of capture, so the data travelled with the file forever after — surviving database migrations, lab-software changes, and the years between original capture and an eventual reprint request. That same metadata-with-the-file discipline carries through to A1SI's current 21 CFR Part 11 work on EMDT (every device record carries its full audit-trail metadata in the file format the inspector sees) and on TERM (every regulated-mode session transcript carries its full chain-of-custody hash chain).
Need to carry a product line forward across a technology shift?
A1SI has been retiring legacy products into modern successors since the early 2000s — film to digital, DOS to Windows, desktop to cloud, single-tenant to multi-tenant. Same engineering posture across the bridge: keep the operator workflow stable, rebuild the technology underneath, ship backwards-compatible data formats so the customer never has to migrate. If your product line is approaching a technology transition, we'd like to hear about it.
"Olan Mills" is a trademark associated with the Olan Mills Studios brand (acquired by Lifetouch / Shutterfly in 2011). "Canon", "Nikon", "Kodak" / "PhotoCD" / "DP-2", "Fuji" / "Fujifilm", and "Sony" are trademarks of their respective camera manufacturers. "Microsoft", "Windows", "Visual Basic", "FoxPro", "Access", "Excel", "Word", and "SQL Server" are trademarks of Microsoft Corporation. "Symbol" and "PDT" are trademarks of Symbol Technologies (acquired by Motorola Solutions in 2007 and now part of Zebra Technologies). The case study above describes engineering work performed by Technical Products Group (TPG, the predecessor business to A1 Systems Integrators) in the ~2002–2017 era. The case study is preserved on this page as historical portfolio and pedigree — not as a currently shipping product offering. A1SI is not affiliated with or endorsed by Olan Mills, Lifetouch, Shutterfly, Canon, Nikon, Eastman Kodak, Fujifilm, Sony, Microsoft Corporation, or any other named third party today; IP ownership of any deployed derivatives belongs to the respective program owners.