i am writing a checklist on what to do if you convert an access 97 to access 2002 or later.
i need for you to write me maybe 10 checklist to make sure the conversion is successful. example, maybe active x control is missing and you have to go to tools/macro editor/reference and check it. I understand that not all conversions will be successful because the older version of access may not be in the newer version.
i need for you to simulate your checklist by writing a simple access97 program with a simple data entry form, simple report, simple macro, simple skin of the form. just simple enough so you can demonstrate your checklist.
and when i convert to access 2002 or later, the formatting is wrong and there will be an error.
now if we follow your checklist, the formatting will be fixed and the error wil be gone.
the checklist needs to be details and easy to understand.
again, it doesnt have to cover EVERYTHING. only the most important features to be checked.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).