Sure.
For me they are of 2 types: Home stuff I programmed to make my wife's
work-life easier, and the programs I do for work.
The ones for my wife are simpler. They involve frontends to
relational databases in Access (with validations, pull down
boxes..etc) and then print forms to a Crystal Report.
A lot of her work is done in a grid (using Infragistics Ultragrid
2.0). A lot of basic stuff like create/delete/edit client, weekly
logs, keep track of which clients made it to classes, print out a
certificate per each client per class, or print a list of which
classes they attented and which classes they still need to take.
Work is actually more of the same, but much larger. We use SQL server
at work. I do a lot more file manipulations (copy, read/write, make,
manipulate..etc).
One program (our largest) has something like 15 forms, 10 modules (to
keep things neat), and about 10 crystal reports.
I probably have about a dozed program out in the building and more
being made regularly.
--
Most of our programs stay the same, with minor bug fixes. The big one
I mentioned is being re-written because of new servers. I'm taking
the oppertunity to remove the data environment and replacing all sql
calls with code, and adding error checking made after the program was
written (the code traps erros and puts them into an error database for
me to folow up on).
The wife's one is about 2 weeks old - so I could literally start from
scratch using .net - but there's the learning curve.
At work there are 2 programmers - myself, and a more sql expert who
also knows vb. His mentality is to stick with vb6 - because it does
everything we need and we know everything we need to.
I'm more along the lines of being waaay behind the technology curve,
so I was thinking about using .net for my own projects at home, and
starting to do some work programs in .net also (after learning curve).
