[AccessD] FW: MS Access Skills Assessment and Testing

hah! I can alwaysvsend you some of my work, especially the early stuff.  A lesson in "pitfalls to avoid". :)  although I have always been excellent with data, relationships and normalisation - there are plenty of design issues ended up biting me!
:)


-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Max Wanadoo
Sent: Tuesday, 12 May 2009 5:40 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] FW: MS Access Skills Assessment and Testing

Hi Andy,
I am well, thank y ou.
Thanks for the suggestions.  The problem is I don't have any code with
faults in it and I don't have any apps that crash.  I have no experience
whatsoever of creating these.  What do I do now?

Max


-----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Andy Lacey
> Sent: Monday, May 11, 2009 6:04 PM
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] MS Access Skills Assessment and Testing
>
> Hi Max, how're you doing?
>
> I used to set a couple of practical tests.
>
> The first was to give them some Access code with faults in it and leave
> them
> for a while asking them to critique it. You can throw in what you want,
> from
> not Dim'ing vars or not closing recordsets to logic or calculation errors.
> Whatever fits your bill.
>
> The second was to give them an app which crashed when you ran it and tell
> them to fix it. Nothing too trivial but it should show problem solving
> capabilities and experience with debug. You could deliberately remove error
> handlers and see if they put them in.
>
> The tests didn't distinguish the good from the great, but they did get rid
> of the blaggers. Had one guy who took exception to being asked to do such
> menial tests when he had blah-blah years experience, but we insisted, put
> him in a quiet room and when I went in half an hour later to see how he was
> doing he'd legged it. Didn't hear from him again.
>
> --
> Andy
>
>
> --------- Original Message --------
> From: "Access Developers discussion and problem solving"
> <accessd at databaseadvisors.com>
> To: "'Access Developers discussion and problem solving'"
> <accessd at databaseadvisors.com>
> Subject: Re: [AccessD] MS Access Skills Assessment and Testing
> Date: 11/05/09 15:15
>
>
> Developer - definitely.
>
> Max
>
>
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Susan Harkins
> Sent: 11 May 2009 15:37
> To: Access Developers discussion and problem solving
> Subject: Re: [AccessD] MS Access Skills Assessment and Testing
>
> I think it depends on how this person's going to use Access -- are they
> going to be a user or a developer?
>
> Susan H.
>
>
> >I would start with a simple database with one form. Set the form up
> >with  some code that does a calculation but set the underlying data so
> >that it  causes an 'Invalid use of Null' or a divide by zero in the
> >calculation  code. Let the candidate debug it while you watch. You
> >should be able to  tell pretty quickly how familiar they are with Access.
> >
> > Doug Steele
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
> ________________________________________________
> Message sent using UebiMiau 2.7.2
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
>
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

This email and any attachments may contain privileged and confidential information
and are intended for the named addressee only. If you have received this e-mail in
error, please notify the sender and delete this e-mail immediately. Any
confidentiality, privilege or copyright is not waived or lost because this e-mail
has been sent to you in error. It is your responsibility to check this e-mail and
any attachments for viruses.  No warranty is made that this material is free from
computer virus or any other defect or error.  Any loss/damage incurred by using this
material is not the sender's responsibility.  The sender's entire liability will be
limited to resupplying the material.