Feedback Questions before submitting new database for independent review

[robess01]

I am close to the completion of the build of an Access 2010 Database. I am not an access programmer but did all the design and configuration work before handing over the project to am access programmer for coding etc. I now need to have the database vetted and checked for best practice issues and design functionality. Before starting this process, however, I would like to frame a specific list of questions to the access programmer to begin the process as well as making sure I am on the right track, with what they need to provide so it can be reviewed.
With this in mind, if you are an access professional, and I was about to send you a finished Access database, what questions would you ask me and how would you want those responses structured so as to ensure you are getting a good workable database design.
Items that seem important to me include:
1) The best format and way I can ask the programmer to provide me with a list of all the source code and notes for all the lines of code. The programmer may not be able to offer ongoing maintenance support and I want to be sure I have full details on the code etc, if I need to appoint a new Access programmer. Is there a standard report or procedure that access programmers use.
2) The best way to protect my ownership of the source code and passwords etc, to prevent the access database being easily pirated?
3) Best practice of Assess design structure. How can I ask and check that the configuration of the database is best practice and not going to produce all sorts of problems down the track?
4) Multiuser environment – database will be installed on various networks with different server configuration and operating systems. How do I obtain information on the how the potential problem of bugs appearing as a result of system conflicts has been handled correctly?

I am sure they are other issues as well. Any help or ideas would be much appreciated.

 

[RainLover]

I don't know what the other people here think, but if you don't know what questions to ask how will you know you are getting a quality answer.

For example who is going to pirate your Database. Most developers would prefer to write their own code not use someone else's. I would not like to be held responsible for something I did not write.

You are installing on a multi user environment. Do you understand what this means. They way you described it does not make senses to me.

I guess I am saying that only through your own experience can you judge others.

 

[ButtonMoon]

1) Properly commented should generally need very minimal documentation.

2) With a licence agreement. You should already have an intellectual property agreement with the developer because otherwise it isn't your IP (but IANAL).

3) Needs to be reviewed by someone with appropriate expertise. There is no substitute for inspecting the design and the code.

4) If that hasn't been tested already then the development isn't done yet. Testing isn't a separate activity, it's all part of developing and delivering code that works.