Dear Sir,

I have completely read and understood your project. I am very well experienced with VB, specially database driven applications. I had made something very similar a while ago which was a banking project. Don't worry about the deadline factor, this wont take much time.

I just have one clarification to make that would make me (and yourself) sure I have understood the project:

1.The Station Diary, Crime Diary, Lock Register and the Accident Register are accessible by the ordinary users and admin users. However, the ordinary users could just add, view, edit, search, print etc through these records but the admin users can do all the above and delete records. When an ordinary user is logged in and tries to delete the record he would get an error. Correct?

2. Now can the users (admin and ordinary) view these forms (Station Diary, Crime Diary, Lock Register and the Accident Register) ONLY when they are logged in? Now you have said you need the Login and Logout options in the Station Diary itself and in NO other form. I have thought of an interface which i think would be apt, as you have given the coder flexibility to think of a good interface. Its something like this:

• When user executes the exe he is prompted with a login screen. He enters from a drop down menu whether he is an admin or a ordinary user, enters his username and password and if correct is forwarded to the logged in form. Now the 'Logged form' is an MDI form. There he has the following options:
  
  File
  --Logout
  --Your Details (Not Mandatory)
  
  Options
  -- Station Diary
  -- Crime Diary
  -- Lock Register
  -- Accident Register
  
  Help  (Not Mandatory)
  -- Help File
  -- About
  
  Now whenever a user clicks on any of the options, that respective form opens. For example, the user clicks on the Station Diary option from the Options menu. The station diary form opens with options to add, view, delete, print  etc etc. Remember, this being an MDI form you could even open all the forms at once and work on them.
  
  I suggest the admin console should be a separate exe altogether, however it depends on you. I could authenticate the super admin (the admin who could access the admin manager) from the login form itself and forward him to a separate admin manager console. That may or may not be an MDI form as the options to offer the user there are quite limited and don't require more than one form.

Now I had a few suggestions/questions too:
1. Can any of the admin users access the admin manager console? Or is that only accessible by a super user? I could store the username and pass of the super user in the registry or a ini file or just hardcode it in the program.

I personally enjoy developing database driven applications so I am really looking forward to do this one. That's the reason i have sent across such a detailed bid as to show you my high level of  interest in this project.

Thanks
Neville