×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Thanks for the tip about iData. But it also underscores that I must not be giving a clear picture of the design pattern I'm using.
Under iData, grid rows and columns map precisely to database table rows and columns.
Contrast that with the model I'm using, where each cell represents the intersection of two separate, but related tables. In my example, each cell represents the intersection of class students, and class assignments tables. The intersecting cell may reference a "record" in a third table. Or, that record may be "missing" - in which case the cell would be empty.
Contrast that with iData, where each cell represents the intersection of a row and column in a single table.
"Worksheet" may be the wrong word to call the design pattern. Would Pivot Table be more accurate? Aaron, you're not the first person to miss the distinction. Which makes me wonder if I'm not describing it properly.
-Nathan.
----- Original Message ----
From: Aaron Bartell <aaronbartell@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Fri, April 9, 2010 3:35:25 PM
Subject: Re: Worksheet Database Maintenance Model
I don't have an exact use case but instead wanted to let you know about
Profound Logic's iData tool which is browser based, allows for cell editing,
and is written in RPG on the server side - pretty cool stuff. Think of it
as a web version of WRKDBF. Downloading and installing it might give you
some ideas on the usefulness of it's features in other business scenarios.
Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/
midrange.com
