[AccessD] Technical test for developers

All those to whom I've sent the test today please note: it is a work in
progress and the test questions document does NOT currently line up exactly
with the Q & A document!! 

I have to have this signed off in an hour so I won't be sending any more
copies out until it is finished - that way you'll get Q's & As that make
sense. Of course any feedback you have will still be interesting even though
I won't be able to make any further changes to the test.

Roz

-----Original Message-----
From: Roz Clarke [mailto:roz.clarke at donnslaw.co.uk] 
Sent: 14 May 2003 09:40
To: 'accessd at databaseadvisors.com'
Subject: RE: [AccessD] Technical test for developers


Thanks John

I've thrown this back to the list to discuss your suggestions.

Regarding the running of SQL statements direct versus passing a string
variable - is there a reason for doing this other than the re-usability of
the variable? I want to be able to explain why I was looking for a certain
thing, and so many of these things are just habits I picked up from the list
without ever fully understanding WHY.

An Excel spreadsheet would be more common but I wanted the typos - you'd be
a lot less likely to get typos in a spreadsheet... But you're probly right
anyway.

Thanks again for the input

Roz

-----Original Message-----
From: John Bartow [mailto:john at winhaven.net] 
Sent: 13 May 2003 21:15
To: Roz Clarke
Subject: RE: [AccessD] Technical test for developers


Roz,

Pretty good test.

A couple of minor suggestions.

You might change your code in Access programming #2 to: db.Execute "INSERT
INTO tblUpdateLog (ulDate, ulRecordCount ) VALUES ( #" & Date & "#, " &
FlagCount & ") " which would show a lack of experience - and then see if
they change it to
use:
---------------------------
Dim strSQL As String
strSQL = "INSERT INTO tblUpdateLog (ulDate, ulRecordCount ) VALUES ( #" &
Date & "#, " & FlagCount & ") " db.Execute strSQL
---------------------------

I also thought the converting a Word table exercise would be better as
converting an Excel spreadsheet exercise - nothing wrong with the original -
I just think an Excel example would be a more common experience. JMO though.

John

> -----Original Message-----
> From: Roz Clarke [mailto:roz.clarke at donnslaw.co.uk]
> Sent: Tuesday, May 13, 2003 11:02 AM
> To: 'John Bartow'
> Subject: RE: [AccessD] Technical test for developers
>
>
> Here you are - no peeking at the answers!
>
> -----Original Message-----
> From: John Bartow [mailto:john at winhaven.net]
> Sent: 13 May 2003 16:57
> To: roz.clarke at donnslaw.co.uk
> Subject: [AccessD] Technical test for developers
>
>
> Hi Roz,
> I'll give it a drive for you.
>
> John B.
>
> -----Original Message-----
> From: accessd-bounces at databaseadvisors.com
> [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Roz Clarke
> Sent: Tuesday, May 13, 2003 10:00 AM
> To: 'accessd at databaseadvisors.com'
> Subject: [AccessD] Technical test for developers
>
>
> I've put together a wee test to give people I'm interviewing for a
> position as a systems developer later in the week.
>
> Not having done this before, I'd be interested in getting some input
> from y'all. This is pitched at people with about 5 years experience, 
> who will be expected to do a lot of work in Access (but nothing very 
> taxing), some light
> (but important) SQL Server dev & admin, a fair amount of Office
> integration
> and ideally will know enough VB to show me a thing or 2.
>
> It should take about half an hour (I think it's probably too long at
> the moment). I'm more interested in intelligent & practical thinking 
> than 100% correct answers (I'll be going through the interviewees' 
> answers with them at length). If you'd be willing to road test it for 
> me let me know and I'll mail you the word doc.
>
> TIA
>
> Roz
>
>
>

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com