Your policy of warranty on your work is spot on and clear. Both my major releases and most of my "Baby" db's have been built on work time so happy to acknowledge the software belongs to them.
As long as you can be sure that the work in production is yours and yours only, I'll happily teach office cat if that's what he wants.
If you're introducing more than 1 person for developing on a piece of software, there should be a clear process and log system in place to track ANY changes with it (I'd also make sure that any person working on my database has proven that they've been trained by Rick).
I don't think i've ever seen a Versioning or tracking video from you Rick. Its not so much usage of Access but more about proper process and planning. Have you done anything like that before?
Sorry, only students may add comments.
Click here for more
information on how you can set up an account.
If you are a Visitor, go ahead and post your reply as a
new comment, and we'll move it here for you
once it's approved. Be sure to use the same name and email address.