Re: Access v dot net

Jerry Boone wrote:
I understand the feeling - it's good to get out and take a walk now
and then.

Do you have an application in mind? I might offer suggestion based
on that if you would rather.

I have two apps in mind. My main one is the salary programme which is
heavily dependent on subforms. Each employee is a parent record while in
the first subform I have a related table which contains salary data.
Each row is a point on the salary range and there are checkboxes for each
month of the day. So say you could have 10 rows x 12 months, so you have
this grid of checkboxes with salary values on the left and a total column on
the right. The user can select up to 12 boxes, one for each month. I put
the subform in a tab control to save space and use another subform to show
the figures.

Now I know from some previous research that you can do a parent/detail setup
in .NET but I like the way that Access presents this info, i.e being able to
drop subform in that I can link to the main form very quickly. The .NET
example I saw meant you show the main records then click a button and the
form with the related tables would popup. In my app that would not work
from the user's point of view.

There isn't much reason to port this to .NET apart from the learning
experience which in itself would be valuable. But maybe it's also an
opportunity to add new features that I'm not even aware of right now, things
that aren't possible with Access.


The other app is my behaviour database which I've posted about here
previously. That's far more conventional and simple. The idea there is to
record details of behaviour incidents involving pupils. I'd also have to
keep track of their changing status (on report, special measures etc) and
other associated details. I think that would be a more likely candidate to
test out .NET.


.