Public sandbox · Cloudflare D1 · sample data only

Issues D1

If you have an Access, Excel or CSV register and want the same list in the browser — and on a phone — use Intake for a small sample CSV, or Contact to describe the file.

Same Issues screen as the localStorage demo, but rows live in a shared D1 database. Anyone on this URL sees the same list. Do not type real names, tickets, or company data. The other tab does not update by itself until the list polls (about 8 seconds) or you click Refresh list. Back to the private localStorage demo.

Open filter is SQL (qselIssuesOpen). Mark Resolved updates tblIssues by primary key. Save uses a Version column (conflict if someone else saved first). What this demo shows · Android app

Open issues (Split · datasheet)

Click a row to load the selected record. Open = Active and status not Resolved or Closed (SQL on the server).

ID Title Status Pri Due

Issue

Lookups store the ID and show the name. Writes need the security check below.

What this demo shows

Android app (sideload, not Play Store). Same shared D1 as this page. Sample data only. Debug-signed APK 0.4.0.

On the phone: allow the browser to install unknown apps, then open the APK. The app pulls first, then sends queued saves. If the website already saved, you choose the website copy or keep yours.

IssuesSandbox.apk

The stack

  1. Microsoft's Issues template -- their sample. Get it from Microsoft featured Access templates. We do not host their .accdb.
  2. Nifty Access Issues gold -- our rebuild of that idea: tblIssues plus status, category, and priority lookup tables (not Microsoft's Contacts table, Filters chrome, attachments, or Related Issues). Same field names as this page and the Android app.
  3. This website -- those tables in the browser, in a shared Cloudflare D1 sandbox (sample data only).
  4. Android app -- same D1, same rows. Sideload the APK above. Not Access running on the phone.

The Access file and these clients share names. Saving here does not write a Jet file on your PC. This sandbox is not a company tenancy.

  • Open filter in SQL -- the server hides Resolved and Closed.
  • Lookup Edit writes to D1 -- Status, Category, and Priority Edit add members with server integer ids. Hide Me sets Active=0; the row stays. Reset seed drops extra members.
  • Version on save -- if someone else saved first, you get a conflict and the row reloads.
  • Unsaved changes -- leave a dirty record and you get Yes / No / Cancel (Access Me.Dirty). Yes waits for the D1 save; if that save fails you stay on the record.

Will this work when the data is in a database?

This page already is a database. The prompt is form behaviour, not localStorage behaviour.

Sample data only. Shared sandbox -- not a company tenancy. Lineage: Microsoft Issues template. Product: Nifty Access conversion. Private-browser twin: /demo/issues/.