[Quimby]

Hey Lis, thanks for your feedback.
You brought up quite a few good points I hadn't considered.
Each time I have developed a program so far, I have been employed by the company.
I don't want to join a team, so I figured that being an employee rather than a contractor would be a less messy situation.
The problem with presenting myself as a contractor would be quoting a final price as I have found with the businesses I have worked for, the final goal keeps changing as more and more people put in thier opinions leading to potentially costly schedule blowouts.
Reading back over my message, I can see how you got confused so I will have to put some more work into it before sending it out.
(What did I misspell by the way? I didn't use a spell checker whilst writing it, but I usually don't have a problem.)
And just to clarify, I have previously worked on rostering / database intergrating / account keeping programs, usually for larger companies.
I have found that if you make fairly rigid but user friendly programs that are flexible and easily altered (by a designated few - usually the companies own IT staff), there is rarely any issues.
The main problem with most places is that key people that had to use them (supervisors and the like) were not very computer literate, so having a consistant and self explanitory program that they could become accustomed to really helped.
In refference to the maintainance issue, I have not actually had to do any additional work to my completed programs so far, but thanks for pointing that out.
I will have to rethink my approach, including maintainance into it.
I make a point of having very user friendly and comprehensive help sections, and in one case an interactive tutorial to help users better understand how to use the programs.
Again, thank you - Much appreciated. :-)